Feature #641
closedallow logs to be piped to an external program
0%
Description
We already support sending logs to syslog, to stdout, or to a file. We could pretty easily support a fourth option, which is piping them to an arbitrary process. This would be slower than the first three, since it would involve more context switches, but some users might find it useful.
One tricky question is what to do if the filter process dies. I guess either respawn it or give up on it. Or maybe respawn it a few times, then give up if it keeps dying?
Updated by Sage Weil about 13 years ago
- Translation missing: en.field_story_points set to 2
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 593
Updated by Sage Weil about 13 years ago
- Translation missing: en.field_story_points changed from 2 to 5
- Translation missing: en.field_position deleted (
593) - Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 593
Updated by Sage Weil about 13 years ago
- Translation missing: en.field_story_points changed from 5 to 3
- Translation missing: en.field_position deleted (
593) - Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 593
Updated by Anonymous over 12 years ago
This is feature creep. If you want to process the logs asap in another process, just have it get ceph stdout as stdin; e.g. runit does this with svlogd. No need to worry about restarts etc.
http://smarden.org/runit/
http://smarden.org/runit/svlogd.8.html
I vote for close as will-not-fix. Ceph is complex enough without all this.