You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[connector/datadog] support obfuscation in datadogconnector (open-telemetry#37457)
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
Support obfuscating SQL and Redis queries in APM stats in Datadog
Connector.
replace statement in otelcontribcol was necessary due to failing build
in pipeline. It doesn't appear that any modules use any affected
functions, but building otelcontribcol with ocb failed due to an API
change. Also opened an issue to bump the `receiver/awscontainerinsight`
dependency so that this replace can be removed in the future: open-telemetry#37486
<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Replaces open-telemetry#35401
<!--Describe what testing was performed and which tests were added.-->
#### Testing
Added TestObfuscate in connector_native_test.go
<!--Describe the documentation added.-->
#### Documentation
added release note and link to semantics on Datadog vendor website
<!--Please delete paragraphs that you did not use before submitting.-->
# 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: datadogconnector
8
+
9
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10
+
note: Support obfuscating sql queries in APM stats
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: [37457]
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
+
Ensure that feature flags "enable_receive_resource_spans_v2" and "enable_operation_and_resource_name_logic_v2"
20
+
are also enabled on both Datadog Exporter and Datadog Connector so that span attributes are properly
21
+
mapped to span type and span resource in Datadog APM; otherwise spans and apm stats may not be
22
+
obfuscated and attributes on stats payloads may not match traces.
23
+
See https://docs.datadoghq.com/opentelemetry/schema_semantics/semantic_mapping/?tab=datadogexporter#mapping-opentelemetry-database-system-type-to-datadog-span-type
24
+
25
+
NOTE: Long/complex SQL queries may cause a performance impact on APM Stats calculation in Datadog Connector.
26
+
Consider implementing sampling in your pipeline prior to sending traces to Datadog Connector if you experience this.
27
+
28
+
# If your change doesn't affect end users or the exported elements of any package,
29
+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
30
+
# Optional: The change log or logs in which this entry should be included.
31
+
# e.g. '[user]' or '[user, api]'
32
+
# Include 'user' if the change is relevant to end users.
33
+
# Include 'api' if there is a change to a library API.
0 commit comments