You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start a service that produces log events into log files.
Problem
Papertrail starts displaying events about 1-2 minutes after the service starts. This is not optimal since we would like to see initial logs when a service is starting (or if it fails to start for example).
Patched Solution
The way we resolved this for now is that we force the init script that registers to Papertrail to sleep for 2 minutes after it's done, and then start executing remote syslog & the service's init script later.
Suggestion
If remote_syslog2 can provide a delay flag, so that it can buffer log events for a configurable amount of time (2 minutes works in our case), and then send everything to Papertrail once the duration is over, that would be a better solution as we won't need to delay our service's init script from running.
The text was updated successfully, but these errors were encountered:
Setup
Whenever a new server starts, the following happens in order:
Problem
Papertrail starts displaying events about 1-2 minutes after the service starts. This is not optimal since we would like to see initial logs when a service is starting (or if it fails to start for example).
Patched Solution
The way we resolved this for now is that we force the init script that registers to Papertrail to sleep for 2 minutes after it's done, and then start executing remote syslog & the service's init script later.
Suggestion
If
remote_syslog2
can provide adelay
flag, so that it can buffer log events for a configurable amount of time (2 minutes works in our case), and then send everything to Papertrail once the duration is over, that would be a better solution as we won't need to delay our service's init script from running.The text was updated successfully, but these errors were encountered: