-
Notifications
You must be signed in to change notification settings - Fork 60
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
Monitoring Framework #25
Comments
I'm thinking some of this would be simpler and more flexible with an event hook system. Example config:
|
There has been no traffic on this. Still worth doing/keeping around as a ticket? |
I still like this idea, but it may be a few released out. |
Are there any plans to do this? It would be extremely useful to have this for jobs with many downstream dependencies. |
I don't think we have any plans to work on this any time soon. We have to figure out how to fix the underlying architectural issues with Tron before we make any additions to it. |
I've started a prototype for monitoring in #335. |
@irskep I'm going to close this ticket, as we have the check_tron_jobs command now. It isn't as flexible as running arbitrary commands for hooks, but it is useful for yelp developers as it uses the same |
OK! I haven't worked on Tron since 2012, so you know best. :-) |
Tron needs a framework for doing monitoring.
Some potential monitoring systems:
Most we need a flexible framework of recording tron events and deciding what to pass onto configured monitors. Some of these may be integrated with how we do the web service framework. As in a nagios monitor could fairly easily use the web service interface to find the status of jobs. However sending an email on a failure would not work well with this system.
We now have support for crash emails, which is part of solving this guy.
Copied from rhettg#2
The text was updated successfully, but these errors were encountered: