-
Notifications
You must be signed in to change notification settings - Fork 5
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
Better monitoring of Fatman's condition #77
Comments
Good scope. I suspect it'll be a bit finicky to design right, because we can't predict what kind of deployment targets will be implemented. So maybe a common framework is the way to do it? Agree on the red/yellow/green. Maybe to begin with only red and green, since yellow becomes a matter of definition and can be subjective? Maybe it's something like this:
This way it's RT that has the responsibility and the job type plugin which has the implementation. |
Let's improve the way of reporting current Fatman's status on Dashboard by extending it with information such as:
This will give a better insight about what's happening with the workload.
Some deployers other than Kubernetes won't have access to these extra data. Therefore it should be achieved in a general way, taking advantage of plugins system.
The plugin should just report status (Green, Yellow or Red) with an
explanation
field, describing the reason of malfunction.The text was updated successfully, but these errors were encountered: