[PLATFORM-1795]: Ensure observability is strong for migration #64
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
cottinisimone
approved these changes
Jun 21, 2024
cpiemontese
deleted the
PLATFORM-1795/task/ensure-observability-is-strong-for-migration
branch
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.
https://prima-assicurazioni-spa.myjetbrains.com/youtrack/issue/PLATFORM-1795
I noticed we still tag with
prima:countryinstead ofprima_country.Even though the
prima_countrytag seems to be added automagically on our metrics, we should still tag them correctly. Also,prima:countrycan't be used to group metrics, onlyprima_countrycan.The other option IMHO is to remove this and simply rely on the base
prima_countrytag from PlatOps