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

Include metrics label to uniquely identify the database #300

Merged
merged 2 commits into from
Dec 10, 2022

Conversation

spilchen
Copy link
Collaborator

@spilchen spilchen commented Dec 8, 2022

Adding a new label to all of the Prometheus metrics that the operator collects. We include the revive instance ID. Here is a sample metric:

vertica_up_nodes_count{namespace="vertica",revive_instance_id="566b8f9590b771272b918c86a17a7b",subcluster="defaultsubcluster",verticadb="vert"} 3

The label revive_instance_id will allow us to match labels generated at the server. This will help allow us to pull metrics into the same dashboard for operator and server.

Adding a new label to all of the Prometheus metrics that the operator
collects. We include the database name: e.g. db_name="vertdb". I am
adding this to be in-sync with the server as it uses the same label.
This will help allow us to pull metrics into the same dashboard for
operator and server.
@spilchen spilchen self-assigned this Dec 8, 2022
This changes earlier commits in the PR. I know use the
revive_instance_id as a unique identifier of metrics for a cluster. This
will be in-sync with the server metrics, so we will be able to associate
operator metrics with the server with the same life of the cluster.
@spilchen spilchen changed the title Include DB name label in Prometheus metrics Include metrics label to uniqely identify the database Dec 9, 2022
@spilchen spilchen changed the title Include metrics label to uniqely identify the database Include metrics label to uniquely identify the database Dec 9, 2022
@spilchen spilchen merged commit 81adcd6 into vertica:main Dec 10, 2022
@spilchen spilchen deleted the prometheus-db-name branch December 10, 2022 01:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant