-
Notifications
You must be signed in to change notification settings - Fork 535
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
Tenant federation implementation of exemplar query interfaces #927
Conversation
41d9956
to
b8e63ad
Compare
Allow queries with multiple tenants against exemplar endpoints. Queries for each tenant are split and run in parallel using the same logic as the existing tenant federation query endpoints. Similar to the existing federated endpoints, the label `__tenant_id__` is added to the set of series labels for each exemplar to indicate which tenant it was queried from. Signed-off-by: Nick Pillitteri <[email protected]>
b8e63ad
to
609eadb
Compare
* Move shared code to common file Signed-off-by: Nick Pillitteri <[email protected]>
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.
Good job! This looks good to me.
I only had one more minor comment about a test name
Better test case names Signed-off-by: Nick Pillitteri <[email protected]>
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.
Thanks for your work on that. Good to close the gaps in federation before we release.
LGTM
Signed-off-by: Nick Pillitteri <[email protected]>
Signed-off-by: Nick Pillitteri [email protected]
What this PR does:
Allow queries with multiple tenants against exemplar endpoints. Queries
for each tenant are split and run in parallel using the same logic as the
existing tenant federation query endpoints.
Similar to the existing federated endpoints, the label
__tenant_id__
isadded to the set of series labels for each exemplar to indicate which tenant
it was queried from.
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]