feat(otelcol/exporter/datadog) Add Datadog exporter wrapper #739
Conversation
This file contains 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
|
|
…ts and finish exporter wrapper
polyrain
force-pushed
the
feat/datadog-exporter
branch
from
7e11654
to
e4f3d61
Compare
# Conflicts: # go.mod # go.sum
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Description
This PR adds a wrapper around the Datadog Exporter from the opentelemetry-collector-contrib repo. It enables use of the Datadog exporter, which allows Alloy to send telemetry (metrics and traces at this point) to Datadog.
This is useful in migrating a Datadog setup towards a more OSS architecture. By allowing Alloy to talk to Datadog, Alloy can serve a new wedge of users using this proprietary platform and embrace OTel more.
Documentation and more tests need to be added, as well as more scrutiny; I intend on continuing work on this branch to address these over the next few days. This MR has dependency on #711 , hence the large diff 😅
Which issue(s) this PR fixes
Fixes #714
Notes to the Reviewer
PR Checklist