-
Notifications
You must be signed in to change notification settings - Fork 176
Make prometheus install for a fresh user #202
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
Conversation
|
We dont need to revert this change here. With our internal usage of prometheus-ksonnet we have the following: So, looks like the issue here is simply that |
|
Came here to say the same thing as @woodsaj. I don't think this is the correct solution unless there were a way to enforce that In this PR (#156) I claim to have made deployment of Prometheus replicas as a statefulset the default, but clearly I didn't add the actual replicas. Re adding |
cstyan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
re-add main_prometheus and double check that that doesn't result in the addition of a third Prometheus instance in one of our clusters
|
@cstyan Thanks. I feel better now - the I'd say that my fix and the |
|
@cstyan switched to your |
| /* | ||
| * All Prometheus resources are contained within a `prometheus` node. This allows | ||
| multiple Prometheus instances to be created by simply cloning this node, like | ||
| so: | ||
| `other_prometheus: $.prometheus {name: "other-prometheus"},` | ||
| To remove the default Prometheus, use this code: | ||
| `main_prometheus: {},` | ||
| */ | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome 👍
Previously, a change was made to make it possible to have multiple Prometheus servers running. This involved two changes: putting everything into a
prometheuswrapper element, and then making that element hidden.The issue is that, for a new user, this introduces a weird behaviour. You get Grafana installed, but no Prometheus. And the reason, for a new Jsonnet user is esoteric:
::vs:.This PR keeps all Prometheus resources inside the new element - this seems like a good practice, as it allows that element to be referenced and cloned, as was the intent of the original change.
However, it makes the
prometheuselement public. That way, newcomers will get the Prometheus server they expect. More experienced users, who want to set up multiple Prometheus servers, can doprometheus:: $.prometheus,which will hide the prometheus node.