Robust Logging Options

Registered by Eric Day on 2009-10-30

A few possible features:
* Integrate with syslog
* Ability to log all jobs including the job handles and clients/workers
* Ability to log the workload or a portion of?
* When starting gearmand if the log file does not exist, it is not created and an error is reported.
* When starting gearmand, it opens the log file after it has changed UID.
* I would like it to open the log file and then change UID allowing the log files to remain writable only by root.
* While gearmand is running, you cannot move the log file and create a new one.
* I would like for it to continue writing to the moved log file and then pick up the new one after a SIGHUP for example.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

...can we get some timestamps on each logged entry too?

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.