local/staging: add prometheus-es-exporter for 7.10 cluster #1068
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Copies the existing exporter configuration. This targets the main elasticsearch service which only targets the coordinating nodes. Also add configuration with production values so that rolling forward to production will see minimal changes After deploying this we need to follow up on the alerting and dashboards using ES metrics since we may now see places where data from both clusters are unintentionally mixed
m90
reviewed
Aug 8, 2023
| @@ -0,0 +1,23 @@ | |||
| es: | |||
| uri: http://elasticsearch-1.default.svc.cluster.local:9200 | |||
There was a problem hiding this comment.
So we gave up on the idea of using a headless service because we just don't know which one to monitor, correct?
There was a problem hiding this comment.
I wonder if we can find out where this service is pointing at?
There was a problem hiding this comment.
I was too unclear in the commit message. This service is identical to the h1 coordinator service. I assume both are "headful"? but maybe this is fine. There doesn't appear to be a need for a headless discovery service with this node configuration unlike the "elasticsearch upstream" chart
m90
approved these changes
Aug 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Copies the existing exporter configuration. This targets the main elasticsearch service which only targets
the coordinating nodes.
Also add configuration with production values so that rolling forward to production will see minimal changes
After deploying this we need to follow up on the alerting and dashboards using ES metrics since we may now see places where data from both clusters are unintentionally mixed