Bug 842684

Summary: RFE: csprocessor log file
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: CSProcessorAssignee: Lee Newson <lnewson>
Status: CLOSED DEFERRED QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 1.xCC: jwulf, lcarlon, mcaspers, misty
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-29 02:38:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joshua Wulf 2012-07-24 13:15:11 UTC 
Possible to get client-side logging? It might look something like this:


Tue 24 Jul 2012 18:24 csprocessor push SPEC: 8025. envers revision YYYY
Tue 24 Jul 2012 18:26 update local spec 8025 to envers revision XXXX

I'm not sure what other information would be useful, or possible, but my immediate use case is being able to isolate when and how things go wrong with the corrupted topic IDs in post-processed specs
Comment 1 Misty Stanley-Jones 2013-05-29 02:38:27 UTC 
It's not a daemon so I really don't see how this is useful. I will defer it for now.