-
Notifications
You must be signed in to change notification settings - Fork 18
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
Specification of Telemetry Metrics API requirements #148
Conversation
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.
A couple of typos but overall it looks okay
We will discuss this PR further in our next meeting on 15th Jan. @brunobat it will be great if you could attend that call. |
sure @Emily-Jiang |
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.
As a general rule, the spec should avoid using the term "support" without also providing a very clear definition of what "support" means each place it is used. I've highlighted one particular place but the term is used in other places as well.
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 better
Specification got refactored, so that common integration requirements are separate top-level section, just as section on configuration properties and APIs. It seemed more convenient to have that information at single location rather that have it spread across metrics and tracing (and common) sections.
Fixes #134.