-
Notifications
You must be signed in to change notification settings - Fork 3
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
As a Pages Operator, I want a prometheus #178
Comments
@davemcorwin can you spell out better what parts you want Pages to own and what parts you want the platform to own? |
|
alerting from logging stack is a potential benefit of our switch to Open Search. There's still a lot to be defined on that portion, but it's feasible that users may be able to define alerts based on cf logs (which include container-level metrics and router logs) |
I don't know enough about the differences between these two options to say for sure. I imagine that for anything custom we could either send to Prometheus or spit out something in the logs that could be used for alerts. The upside of Prometheus is that some systems have libraries for exporting metrics to Prometheus that could drop in, like for our background job library. |
yeah, this definitely sounds more like what prometheus is for. |
hmmmm, ok, my thought was this wouldn't require an SCR, since after our SCR we are actually part of cloud.gov. |
It might not, but I think it will - we'll need to define a new authentication mechanism for this (since we don't have proper RBAC on the prometheus stack) and a new alert path, both of which seem likely to me to trigger an SCR |
OK, maybe we can touch base about it, I don't understand why those changes would necessary or SCR-worthy. |
In order to have better alerting, Corwin and friends want Pages Prometheus
Acceptance Criteria
Security considerations
This will improve security because alerts!
Implementation sketch
The text was updated successfully, but these errors were encountered: