[receiver/datadogreceiver] Adding logs support to the datadog receiver #43841
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib. Important reminders:
A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better! |
Co-Authored-By: Robin Law <[email protected]>
…lector-contrib into ddreceiver_logs
atoulme
approved these changes
Nov 1, 2025
Contributor
atoulme
left a comment
There was a problem hiding this comment.
nothing jumps at me, everything LGTM - this is alpha and I haven't tested it myself.
…lector-contrib into ddreceiver_logs
…lector-contrib into ddreceiver_logs
Contributor
Author
|
Could somebody approve my workflows to run please? |
Contributor
|
Thank you for your contribution @bvigar! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey. If you are getting started contributing, you can also join the CNCF Slack channel #opentelemetry-new-contributors to ask for guidance and get help. |
jelly-afk
pushed a commit
to jelly-afk/opentelemetry-collector-contrib
that referenced
this pull request
Nov 6, 2025
open-telemetry#43841) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adding a feature to the datadog receiver to support logs, in addition to the currently supported traces and metrics. This change adds support for the `api/v2/logs` endpoint. Note: There's purposefully no datadog semantics or conforming in this changeset because I plan to make those changes next in the [ddsemanticsprocessor](https://github.com/Sawmills/opentelemetry-collector-contrib/tree/e70d1b2ba66405e10dfc02afc170f8e2462b4a36/processor/datadogsemanticsprocessor). I didn't think they belonged here. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing - Built a custom collector locally with these changes and verified with the debug exporter that otel logs are being exported properly - Added tests for the log translation layer - Added e2e tests for the receiver for single and multiple logs <!--Describe the documentation added.--> #### Documentation Updated the `receiver/datadogreceiver/README.md` to now show support for logs. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Robin Law <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adding a feature to the datadog receiver to support logs, in addition to the currently supported traces and metrics. This change adds support for the
api/v2/logsendpoint.Note: There's purposefully no datadog semantics or conforming in this changeset because I plan to make those changes next in the ddsemanticsprocessor. I didn't think they belonged here.
Link to tracking issue
Fixes
Testing
Documentation
Updated the
receiver/datadogreceiver/README.mdto now show support for logs.