Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support for a 'last run' file #3

Open
kitchen opened this issue Sep 26, 2012 · 1 comment
Open

support for a 'last run' file #3

kitchen opened this issue Sep 26, 2012 · 1 comment

Comments

@kitchen
Copy link
Contributor

kitchen commented Sep 26, 2012

provide support for a 'last run' file, which will be touched when a cron successfully finishes running.

not sure if this is just something which the job should spit out itself and then be stored in logstash or what.

it's an interesting idea though.

@kitchen
Copy link
Contributor Author

kitchen commented Sep 26, 2012

would also have to provide support for user-configurable 'ok' exit codes. for instance, if the job is running rsync, there are several rsync exit codes which I, personally, don't care about under most circumstances, so I would want those to be reported as successful runs.

On the flip side, that might just be something you'd want to pull out of logstash as a report, and can have a nagios check on that. The flipside is that implementing the 'last run' file is a pretty trivial exercise and doesn't require people to have the whole logstash infrastructure set up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant