-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Update log collection #3017
Update log collection #3017
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3017 +/- ##
=======================================
Coverage 91.55% 91.55%
=======================================
Files 464 464
Lines 22846 22846
=======================================
+ Hits 20916 20917 +1
+ Misses 1437 1436 -1
Partials 493 493
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@@ -14,11 +14,11 @@ receivers: | |||
id: get-format | |||
routes: | |||
- output: parser-docker | |||
expr: '$$record matches "^\\{"' |
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.
Please also remember to update the helm chart.
Follows [#88 (opentelemetry-log-collection)](open-telemetry/opentelemetry-log-collection#88) and [#3017 (opentelemetry-collector-contrib)](open-telemetry/opentelemetry-collector-contrib#3017)
Updates `opentelemetry-log-collection` to [v0.17.0](https://github.com/open-telemetry/opentelemetry-log-collection/releases/tag/v0.17.0)
…ng it up (#3597) Split off from PR #3017, as requested to firstly add the implementation unwired to the exporter itself to help the reviewers easily understand Uses an off the shelf WAL implementation to add capabilities to the Prometheus remote exporter using github.com/tidwall/wal. By default the WAL will be on and to configure the WAL location, please use this prometheusremotewrite exporter YAML configuration: ```yaml exporters: prometheusremotewrite: endpoint: "http://some.url:9411/api/prom/push" wal: directory: ./waldir/wal_directory truncate_frequency: 200s cache_size: 300 ``` whose fields are quite similar to Prometheus' WAL fields per https://docs.google.com/document/d/1cCcoFgjDFwU2n823tKuMvrIhzHty4UDyn0IcfUHiyyI/edit#heading=h.mlf37ibqjgov We are using an off-the-shelf WAL because: By the time that we get OTLP metrics, we can convert to Prometheus proto, but trying to implement the Prometheus storage interfaces would involve either by-passing to-Prometheus-Proto and then save to Prometheus raw Go, then retrieve Prometheus raw Go and then convert to Prometheus Proto. It is much easier to get an off the shelf WAL implementation and add it to the Prometheus implementation. The next PR after this one will involve hooking it into the actual Prometheus Remote Write exporter. Updates open-telemetry/prometheus-interoperability-spec#9
Updates
opentelemetry-log-collection
to v0.17.0