-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
AzureMonitor: Support multi-resource aliases and subscription aliases #68648
Conversation
- Add subscription response type - Update AzureMonitorQuery type - Update docs - Update tests - Add function to retrieve subscription display name if not present
Backend code coverage report for PR #68648
|
Frontend code coverage report for PR #68648 |
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
This comment was marked as duplicate.
This comment was marked as duplicate.
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-68648-to-v10.0.x origin/v10.0.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x bca8428f639613e35e9ad61728e0f11841d6b6ad
# Push it to GitHub
git push --set-upstream origin backport-68648-to-v10.0.x
git switch main
# Remove the local backport branch
git branch -D backport-68648-to-v10.0.x Then, create a pull request where the |
…on aliases (#68823) AzureMonitor: Support multi-resource aliases and subscription aliases (#68648) Update legend aliases - Add subscription response type - Update AzureMonitorQuery type - Update docs - Update tests - Add function to retrieve subscription display name if not present (cherry picked from commit bca8428)
This PR adds support for two things:
New functionality has been added to retrieve the subscription name based off of the subscription ID to avoid running a migration in the front-end. These requests are efficient and are only executed if the display name is not already available to the datasource instance.
Legend aliases are now based on the current resource (based on the resource URI) rather than relying on just the ID returned in the series.
Fixes grafana/support-escalations#5920
Fixes grafana/support-escalations#5964