Skip to content

Commit b3e952f

Browse files
authored
[exporter/datadogexporter] Add support for custom log source (#35051)
**Description:** This PR updates `github.com/DataDog/datadog-agent/comp/otelcol/otlp/components/exporter/logsagentexporter` to include commit: DataDog/datadog-agent@09b07eb. This adds support for setting a custom log source from resource attribute or log attribute `datadog.log.source`. **Link to tracking Issue:** <Issue number if applicable> **Testing:** Tested this locally by sending logs with attribute `datadog.log.source` and ensuring this was used as the source. **Documentation:** Updated datadog exporter README.
1 parent 0ceefaa commit b3e952f

File tree

2 files changed

+41
-0
lines changed

2 files changed

+41
-0
lines changed
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Use this changelog template to create an entry for release notes.
2+
3+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4+
change_type: enhancement
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: datadogexporter
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: Add support for setting a custom log source from resource attribute `datadog.log.source`
11+
12+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13+
issues: [35051]
14+
15+
# (Optional) One or more lines of additional information to render under the primary note.
16+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17+
# Use pipe (|) for multiline entries.
18+
subtext:
19+
20+
# If your change doesn't affect end users or the exported elements of any package,
21+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22+
# Optional: The change log or logs in which this entry should be included.
23+
# e.g. '[user]' or '[user, api]'
24+
# Include 'user' if the change is relevant to end users.
25+
# Include 'api' if there is a change to a library API.
26+
# Default: '[user]'
27+
change_logs: []

exporter/datadogexporter/README.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,3 +72,17 @@ To get the service field correctly populated in your logs, you can specify servi
7272
[alpha]:https://github.com/open-telemetry/opentelemetry-collector#alpha
7373
[contrib]:https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
7474
[AWS]:https://aws-otel.github.io/docs/partners/datadog
75+
76+
### How to add custom log source
77+
78+
In order to add a custom source to your OTLP logs, set resource attribute `datadog.log.source`. This feature requires `exporter.datadogexporter.UseLogsAgentExporter` feature flag to be enabled (now enabled by default).
79+
80+
Example:
81+
```
82+
processors:
83+
transform/logs:
84+
log_statements:
85+
- context: resource
86+
statements:
87+
- set(attributes["datadog.log.source"], "otel")
88+
```

0 commit comments

Comments
 (0)