-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
enhancement(ux)!: Use external tagging for metrics serialization #2231
Conversation
Signed-off-by: Alexander Rodin <rodin.alexander@gmail.com>
Signed-off-by: Alexander Rodin <rodin.alexander@gmail.com>
Signed-off-by: Alexander Rodin <rodin.alexander@gmail.com>
Signed-off-by: Alexander Rodin <rodin.alexander@gmail.com>
Signed-off-by: Alexander Rodin <rodin.alexander@gmail.com>
I've updated the Schema section in the metrics data model description, so now all kinds of metrics are documented as top-level fields. The fact that only one object of each kind can be present in a metric now mentioned in the beginning of the section. Not sure is it possible or necessary to separate "one of" fields ( |
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.
Looks good!
I don't think so. Looks good to me. |
This is a small change that closes #2021.
One reason to have it is that it would make metrics representation in
stdout
sink consistent with it in Lua transform. However, it might break compatibility for those who rely on this serialization.