-
Notifications
You must be signed in to change notification settings - Fork 153
fix(metrics): skip empty string dimension values #3319
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
fix(metrics): skip empty string dimension values #3319
Conversation
addDimension
& addDimensions
addDimension
& addDimensions
addDimension
& addDimensions
addDimension
& addDimensions
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.
Thank you for the revisions @arnabrahman!
The friends at the Python version told me they already merged the change and used a slightly different wording in the warning log, which you can see here and is this:
The dimension {name} doesn't meet the requirements and won't be added. Ensure the dimension name and value are non empty strings"
As last step before merging, could you please change to this?
I'll merge right after, sorry I missed the change on their part and didn't point it out in my first review of your PR.
|
It's ok, i have updated the warning message. |
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 addressing the feedback, let's merge it!
addDimension
& addDimensions
Summary
When adding a dimension to my metrics, I should get a warning if the dimension value is invalid aka an empty string ("") or undefined/null, and the dimension should not be added to the EMF blobs emitted by the utility.
Changes
empty
,undefined
&null
values for dimension and if found log warningaddDimension
&addDimensions
Issue number: #3302
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.