-
Notifications
You must be signed in to change notification settings - Fork 6
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
tagging and gauge operations #229
Conversation
Thank you for you contribution @gandarez! Tags are fairly self-explanatory, but can you explain a little more about what the gauge changes are for please? |
@martincostello thanks! Fo all the comments you've done I already fixed them locally. There are only two left I'd need your assistance. The first is about the I followed the documentation for gauges and implemented the concept of being able to change the sign for a gauge. |
@martincostello please be adivised that I needed to add |
@@ -1,4 +1,5 @@ | |||
{ | |||
keyNameSanitize: false, |
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.
If this is needed to make tags work in general, we'd probably want this documented somewhere in the README.
Which reminds me, the README would also need to be updated to mention the tagging capabilities.
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.
Some guidance in the need to use keyNameSanitize
if using tags would still be useful in the README.
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.
I think it should be always false since the tests cover tags and the StatsD server is mocked. In real life this flag does not exist, for instance when running on Graphite.
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.
It's not a mock, it's the real thing:
Any news here guys? |
I'm looking forward to having a fine-grained metrics with tags. Is there an approximate date for version 5.0.0? |
Sorry, there's no planned release date at this time. This is something we'll pick up in more detail when we have the capacity for it. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
The PR will be clossed automatically soon.. no plans yet?? |
Hi @gandarez - sorry for the lack of movement on this PR. For tag support, we're going to take the change from #269 as it is implemented in a more extensible way for a range of different metrics providers. Once that is merged, if you update this PR to just suggest changes to gauges, we can re-review this PR. Thanks! |
This comment has been minimized.
This comment has been minimized.
#312 to add tagging support has been merged. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Related to the issues 175 and 176.