Azure/Insights: Fix handling of legacy dimension values #27513
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
marefr
requested review from
wbrowne and
kylebrandt
and removed request for
a team
marefr
changed the title
hugohaggmark
pushed a commit
that referenced
this pull request
Sep 17, 2020
This was referenced Sep 17, 2020
hugohaggmark
pushed a commit
that referenced
this pull request
Sep 17, 2020
ryantxu
pushed a commit
that referenced
this pull request
Nov 18, 2020
Properly handle legacy dimension values in the backend. Fixes #27512
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.
What this PR does / why we need it:
Properly handle legacy dimension values in the backend.
Which issue(s) this PR fixes:
Fixes #27512
Special notes for your reviewer: