-
Notifications
You must be signed in to change notification settings - Fork 11
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
DO NOT MERGE: Add WIP exemplar storage #5
Conversation
I'm a little confused on what the next steps for this feature are. The PR here is to merge into the |
Ah, sorry, didn't read the PR descrpition 🙃 If the point is for people to play around with it, does it really need to go into master? |
@rfratto no I meant to open the PR against our 2.17.1 branch but the github UI was being janky. |
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.
LGTM for playing around with a WIP, minus the conflicts that need to be fixed.
If we're adding this in the agent, we'll need a follow up PR with the vendor update to add the exemplar storage into the agent's instances.
We haven't discussed this yet as part of our downstream repo strategy, but dealing with conflicts caused by other feature branches seems tricky. If you rebase, then the upstream PR will include all our other features. I think the "right" way to do this is manually merging at the command line and fixing conflicts at merge time? It's a pain but that's the only thing I can think of. |
@rfratto pretty easy to fix, I just needed to rebase to our 2.17.1 branch instead of upstream 2.17.1 I didn't expect there to be merge conflicts so I didn't choose that as the base branch initially. I don't have plans to put this into the agent in the near future, just deploy to a single instance in one environment for now. |
If that's the case then @cstyan, I don't see a reason to include it in the release-x branch. You should be able to just run it directly from your branch right? |
Similarly to the WAL watcher, its purpose is to observe the scrape manager and pull metadata. Then, send it to a remote storage. Signed-off-by: gotjosh <josue@grafana.com>
Signed-off-by: gotjosh <josue@grafana.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
ExtractSelectors function returns an array of arrays. Include a test. Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
ExemplarAppender. Signed-off-by: Callum Styan <callumstyan@gmail.com>
bounds panic. Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
querier Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
Signed-off-by: Callum Styan <callumstyan@gmail.com>
@gotjosh I guess so. Could just go back to basing off 2.17.1 and run that. Without really thinking I just thought this had to be merged into something :D |
Signed-off-by: Callum Styan <callumstyan@gmail.com>
Should this be closed, as exemplars were merged upstream? |
Want to put the WIP exemplar storage into one of our environments so people can play around with it.
Note: at the moment this is just my branch for the upstream PR plus the latest commit to add relabelling.