feat: expose prometheus metrics from operator #138
Merged
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
Now the operator exposes a prometheus scrape endpoint. It does not try to push its metrics over OTLP. This operator is long lived so this should not be a problem. The runner continues to push its metrics over OTLP which is important since it is short lived. However I was not able to get both prometheus scrape and OTLP push working on the same process. So the operator only supports prometheus and the runner only support OTLP push.
3benbox
suggested changes
Feb 1, 2024
| requests_status_codes_total.as_any(), | ||
| requests_duration_percentiles.as_any(), | ||
| simulation_min_peer_requests_per_second.as_any(), | ||
| ]; |
common/src/telemetry.rs
Outdated
| Ok((meter, shutdown, join)) | ||
| } | ||
|
|
||
| // /metrics scrape endpoin |
There was a problem hiding this comment.
comment spelling, "endpoint" 😇
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.
Now the operator exposes a prometheus scrape endpoint. It does not try to push its metrics over OTLP. This operator is long lived so this should not be a problem.
The runner continues to push its metrics over OTLP which is important since it is short lived.
However I was not able to get both prometheus scrape and OTLP push working on the same process. So the operator only supports prometheus and the runner only support OTLP push.