-
Notifications
You must be signed in to change notification settings - Fork 25
INFOPLAT-1575 Implement Prometheus to OTel metrics Forwarder #1013
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
Conversation
0b5d061 to
f041f3f
Compare
f041f3f to
b2e263e
Compare
b2e263e to
09fdd3d
Compare
82ad449 to
f0f83de
Compare
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.
How did we end up more than doubling (+150) our dependencies? Are these all from otel?
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.
The k8s deps in particular are concerning. We have had enough trouble with those just in our test modules. I don't think we can allow it to infect everything like this.
e2a6530 to
99919ac
Compare
|
This PR is stale because it has been open 30 days with no activity. |
|
This PR has been automatically closed because it has been stale for > 30 days. |
Implement Prometheus to OTel metrics conversion and export.
Forwarder:
Receiver:
prometheus.Gatherer(same process memory, no HTTP calls)prometheus.scraper(from here INFOPLAT-1575 Implement metric scraper from prometheus.Gatherer pkcll/prometheus#1) to shortcut HTTP request calls and fetch data fromprometheus.GathererExporter:
Upstream PR's
Downstream PR's
Run Example
OTel Collector logs with exported test metric
TestExample_test_counter_metric