-
Notifications
You must be signed in to change notification settings - Fork 2.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
Introduce metricsConsumer and gaugeMetricConsumer. #5426
Introduce metricsConsumer and gaugeMetricConsumer. #5426
Conversation
f466330
to
900c332
Compare
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
@oppegard @thepeterstone please review as codeowners. |
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.
Travis and I reviewed this in person, and pushed a commit with some formatting changes. lgtm.
c21c3de
to
35089c0
Compare
35089c0
to
789ed57
Compare
Hi. It appears that |
789ed57
to
ae68125
Compare
Description:
This is the first pull request for adding a tanzu observability metrics exporter.
This PR introduces the metricsConsumer type which consumes pdata.Metrics instances by sending the metrics within to
tanzu observability.
A metricsConsumer instance is made up of multiple metricConsumer instances. Each metricConsumer instance consumes
a specific type of metric such as Gauge, Sum, or Histogram.
This PR also introduces a function that returns a metricConsumer that consumes gauge metrics.
Future PRs will introduce new implementations of metricConsumer. Each new implementation will consume a different type
of metric.
Testing:
Unit tests only. The instances that will send data to tanzu observability are interfaces. The unit tests create mock
implementations of these interfaces and verify that the right calls were made to them.