Add a new metrics indexing behavior #2
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
Take job_metrics.json from release periodics and simplify into
a map where the key is a prometheus metric + optional labels
(foo{bar="baz"}) and the value is a struct with the float value
as a string (like prometheus returns) and an int64 unix timestamp
which was the timestamp of the query value. Write that map to GCS
with a key suitable for time based indexing inside the source
bucket. This index will be used to fetch metrics by job and display
comparisons in ci-search.
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.
Take job_metrics.json from release periodics and simplify into
a map where the key is a prometheus metric + optional labels
(foo{bar="baz"}) and the value is a struct with the float value
as a string (like prometheus returns) and an int64 unix timestamp
which was the timestamp of the query value. Write that map to GCS
with a key suitable for time based indexing inside the source
bucket. This index will be used to fetch metrics by job and display
comparisons in ci-search.