-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add Datadog Exporter #25035
Add Datadog Exporter #25035
Conversation
// APIConfig defines the API configuration options | ||
type APIConfig struct { | ||
// Key is the Datadog API key to associate your Agent's data with your organization. |
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.
This config is same as Datadog exporter config. In future we should ensure both exporters use same config.
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv create-vm --pipeline-id=33669179 --os-family=ubuntu |
Regression DetectorRegression Detector ResultsRun ID: 7e1677ae-4db0-4185-a527-f277d9511792 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | file_to_blackhole | % cpu utilization | +3.21 | [-2.67, +9.09] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | file_to_blackhole | % cpu utilization | +3.21 | [-2.67, +9.09] |
➖ | file_tree | memory utilization | +1.64 | [+1.52, +1.76] |
➖ | process_agent_real_time_mode | memory utilization | +0.36 | [+0.31, +0.41] |
➖ | otel_to_otel_logs | ingress throughput | +0.09 | [-0.28, +0.46] |
➖ | process_agent_standard_check | memory utilization | +0.07 | [+0.01, +0.13] |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.04 | [-0.16, +0.24] |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.03 | [-0.01, +0.07] |
➖ | trace_agent_json | ingress throughput | -0.00 | [-0.01, +0.01] |
➖ | trace_agent_msgpack | ingress throughput | -0.01 | [-0.02, +0.01] |
➖ | idle | memory utilization | -0.16 | [-0.21, -0.11] |
➖ | process_agent_standard_check_with_stats | memory utilization | -0.17 | [-0.22, -0.12] |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.33 | [-3.17, +2.51] |
➖ | basic_py_check | % cpu utilization | -0.46 | [-3.04, +2.13] |
➖ | tcp_syslog_to_blackhole | ingress throughput | -1.25 | [-22.57, +20.08] |
➖ | pycheck_1000_100byte_tags | % cpu utilization | -1.73 | [-6.20, +2.75] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
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.
One meta comment: a bunch of the configs do not apply to otel agent, e.g. logs.dump_payloads
host_metadata
etc. If those are set should they result in config warnings?
@songy23 We should aim to have same config for both DD exporter in Agent vs DD exporter in collector. Hence I tried to replicate all the config. Some of the config would be noop for OTel agent |
Yes - my point is we should warn the users in config_warnings for configs that are no-op in OTel agent. Otherwise they will wonder why the same config has effect in collector contrib but not in otel agent. |
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.
Discussed offline, will make the change above in a follow-up PR.
comp/otelcol/otlp/components/exporter/datadogexporter/factory.go
Outdated
Show resolved
Hide resolved
lf := logsagentexporter.NewFactory(logch) | ||
lc := &logsagentexporter.Config{ | ||
OtelSource: "otel_agent", | ||
LogSourceName: "otelcol", |
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.
LogSourceName: "otelcol", | |
LogSourceName: "otlp_log_ingestion", |
as we discussed
lf := logsagentexporter.NewFactory(logch) | ||
lc := &logsagentexporter.Config{ | ||
OtelSource: "otel_agent", | ||
LogSourceName: "otelcol", |
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.
This should be set to logsagentexporter.logSourceName
("OTLP log ingestion") to be consistent
/merge |
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.
LGTM for ci-experience files
🚂 MergeQueue Pull request added to the queue. There are 6 builds ahead! (estimated merge in less than 3h) Use |
❌ MergeQueue Build pipeline has failing jobs for c3765c9 Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail. You should have a look at the pipeline, wait for the build to finish and investigate the failures.
|
/merge |
🚂 MergeQueue Pull request added to the queue. There are 2 builds ahead! (estimated merge in less than 1h) Use |
What does this PR do?
The PR adds Datadog Exporter . It is thin wrapper around other exporter we have.
Datadog Exporter in Agent and Datadog Exporter in collector will share the code for exporting each data type .
We can't convert DD exporter as module at the moment as it has other agent dependencies. Will do so in the future PRs.
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes