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
**Description:** <Describe what has changed.>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
The PR creates `pkg/datadog` package with configuration for DD Exporter
and DD connector.
The PR currently retains tests in `exporter/datadogexporter` &
`connector/datadogconnector` . These will be remove along with the
configuration in exporter & connector.
---------
Co-authored-by: Yang Song <[email protected]>
# 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: deprecation
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: |
11
+
The datadog exporter config has been deprecated in favor of the new `datadog/config` package. The new package is shared between the Datadog exporter and the Datadog Connector.
12
+
13
+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
14
+
issues: [35067]
15
+
16
+
# (Optional) One or more lines of additional information to render under the primary note.
17
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
18
+
# Use pipe (|) for multiline entries.
19
+
subtext: |
20
+
The new `datadog/config` package is a shared module for Datadog exporter configuration. The module is shared between the Datadog exporter and the Datadog Connector.
21
+
22
+
# If your change doesn't affect end users or the exported elements of any package,
23
+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
24
+
# Optional: The change log or logs in which this entry should be included.
25
+
# e.g. '[user]' or '[user, api]'
26
+
# Include 'user' if the change is relevant to end users.
27
+
# Include 'api' if there is a change to a library API.
// If set to true, enables an additional stats computation check on spans to see they have an eligible `span.kind` (server, consumer, client, producer).
44
-
// If enabled, a span with an eligible `span.kind` will have stats computed. If disabled, only top-level and measured spans will have stats computed.
45
-
// NOTE: For stats computed from OTel traces, only top-level spans are considered when this option is off.
46
-
// If you are sending OTel traces and want stats on non-top-level spans, this flag will need to be enabled.
47
-
// If you are sending OTel traces and do not want stats computed by span kind, you need to disable this flag and disable `compute_top_level_by_span_kind`.
// If set to true, root spans and spans with a server or consumer `span.kind` will be marked as top-level.
51
-
// Additionally, spans with a client or producer `span.kind` will have stats computed.
52
-
// Enabling this config option may increase the number of spans that generate trace metrics, and may change which spans appear as top-level in Datadog.
53
-
// ComputeTopLevelBySpanKind needs to be enabled in both the Datadog connector and Datadog exporter configs if both components are being used.
// BucketInterval specifies the time interval size of aggregation buckets that aggregate the Datadog trace metrics.
81
-
// It is also the time interval that Datadog trace metrics payloads are flushed to the pipeline.
82
-
// If you are concerned about the metric volume generated by the Datadog connector and the resulting networking egress, try increasing bucket_interval.
0 commit comments