feat(mezmo_datadog_agent_parser): Create MezmoDatadogAgentParser#49
Merged
biblicalph merged 3 commits intomasterfrom Jan 28, 2026
Merged
feat(mezmo_datadog_agent_parser): Create MezmoDatadogAgentParser#49biblicalph merged 3 commits intomasterfrom
biblicalph merged 3 commits intomasterfrom
Conversation
biblicalph
force-pushed
the
biblicalph/LOG-22997
branch
2 times, most recently
from
39a967b to
89057ec
Compare
The transform receives a log event and outputs a single or multiple events to one of logs, metrics, traces or _unmatched ouptuts. The Datadog agent data is not decoded by this transform; the incoming event is assumed to be already decoded. For traces, each event is assumed to be an entry of the tracerPayloads or traces (legacy) field of the agent payload. For metrics, each event is assumed to be an entry of the series field of the agent payload. The implementation of the transform is mostly based on the Datadog agent source. Ref: LOG-22997
biblicalph
force-pushed
the
biblicalph/LOG-22997
branch
from
89057ec to
36ebe26
Compare
mdeltito
reviewed
Jan 27, 2026
biblicalph
commented
Jan 27, 2026
|
|
||
| parser.build_events_from_messages(event, output_messages) | ||
| parser | ||
| .build_events_from_payloads(event.clone(), output_messages) |
Contributor
Author
There was a problem hiding this comment.
Clone is still needed here because the method mutates the event
1. Reduce cost of cloning event when emitting multiple events for a received metric or trace 2. Implement trait for transforming event 3. Move event into transform to reduce cloning. 4. On error, move the error into the event 5. Route the original event to unmatched if transforming fails. Previously this was done for logs only. Ref: LOG-22997
biblicalph
force-pushed
the
biblicalph/LOG-22997
branch
4 times, most recently
from
1313aa2 to
6e1bf69
Compare
The vector documentation now includes the two flags for Datadog logs and metrics - likely in newer Vector versions. This matches the implementation. Ref: LOG-22997
biblicalph
force-pushed
the
biblicalph/LOG-22997
branch
from
6e1bf69 to
6b1e115
Compare
mdeltito
approved these changes
Jan 28, 2026
Member
mdeltito
left a comment
mdeltito
left a comment
There was a problem hiding this comment.
looking good for the first cut 👍
Contributor
|
🎉 This PR is included in version 6.7.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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.
This PR adds support for transforming Datadog agent events into logs, metrics, traces and sketches.
This allows us to deprecate VRL handling of metrics while adding support for Datadog traces and sketches.
For reference the following protos apply:
Upstream of vector, the agent payload is intercepted, decoded and normalized. The transform thus expects TracerPayload item for trace events, Sketch for sketch metrics, MetricSeries for metrics and Log for logs.
The implementation is mostly based on the existing Datadog agent source implementation; we don't use that source because it exposes an http server to collect metrics
Ref: LOG-22997
Summary
Vector configuration
How did you test this PR?
Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
Notes
@vectordotdev/vectorto reach out to us regarding this PR.pre-pushhook, please see this template.cargo fmt --allcargo clippy --workspace --all-targets -- -D warningscargo nextest run --workspace(alternatively, you can runcargo test --all)git merge origin masterandgit push.Cargo.lock), pleaserun
cargo vdev build licensesto regenerate the license inventory and commit the changes (if any). More details here.