-
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
[exporter/datadog] Migrate logs exporter from HTTP client to logs agent #30099
Comments
@liustanley is working on this (looks like I cannot assign this issue to you, so just an FYI) |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@liustanley @songy23 any updates on this issue? |
This is still ongoing, added |
…er (#32327) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> This PR adds support for the logs agent exporter in order to export logs to Datadog. The following changes were made in order to support this: - Update datadog-agent modules to the following commit hash version: DataDog/datadog-agent@a1ef7ed - Remove `peer_service_aggregation` config option which was deprecated and removed since last datadog-agent version: DataDog/datadog-agent#23284 - Add logs agent exporter setup in datadog exporter factory. This is disabled by default and can be enabled via feature gate. **Link to tracking Issue:** Fixes #30099 **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.> --------- Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
Component(s)
exporter/datadog
What happened?
This is a tracking issue on the ongoing refactor of the Datadog logs exporter. Currently the Datadog logs exporter uses the HTTP client to send logs and the HTTP client has some issues, e.g. when attributes
a.b.c
anda.b
are both sent,a.b
gets overridden. We want to refactor the logs agent in Datadog-agent and use it in Datadog logs exporter instead.Collector version
mainline
Environment information
No response
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: