forked from open-telemetry/opentelemetry-collector-contrib
-
Notifications
You must be signed in to change notification settings - Fork 0
/
config.yaml
259 lines (226 loc) · 12.1 KB
/
config.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
receivers:
nop:
processors:
nop:
exporters:
datadog:
## @param hostname - string - optional
## A custom hostname.
## If unset it will be determined from the `DD_HOST` environment variable (Deprecated: [v0.47.0] set environment variable explicitly on configuration instead).
## If both this and `DD_HOST` are unset, this will be determined automatically if possible.
#
# hostname: customhostname
## @param env - string - optional
## The environment for unified service tagging.
## Deprecated: [v0.49.0] Set `deployment.environment` semconv instead, see https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/9016 for details.
## This option will be removed in v0.52.0.
## If unset it will be determined from the `DD_ENV` environment variable (Deprecated: [v0.47.0] set environment variable explicitly on configuration instead).
#
# env: prod
## @param service - string - optional
## The service for unified service tagging.
## Deprecated: [v0.49.0] Set `service.name` semconv instead, see https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/8781 for details.
## This option will be removed in v0.52.0.
## If unset it will be determined from the `DD_SERVICE` environment variable (Deprecated: [v0.47.0] set environment variable explicitly on configuration instead).
#
# service: myservice
## @param version - string - optional
## The version for unified service tagging.
## Deprecated: [v0.49.0] Set `service.version` semconv instead, see https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/8783 for details.
## This option will be removed in v0.52.0.
## If unset it will be determined from the `DD_VERSION` environment variable (Deprecated: [v0.47.0] set environment variable explicitly on configuration instead).
#
# version: myversion
## @param tags - list of strings - optional - default: []
## The list of tags to send as host tags.
## Deprecated: [v0.49.0] Use `host_metadata::tags` instead.
## This option will be removed in v0.52.0.
## If unset it will be determined from the `DD_TAGS` environment variable, specified
## as a list of space-separated strings (Deprecated: [v0.47.0] use 'env' config source instead).
#
# tags: []
## @params send_metadata - boolean - optional - default: true
## Deprecated: [v0.49.0] Use `host_metadata::enabled` instead.
## This option will be removed in v0.52.0.
#
# send_metadata: true
## @params use_resource_metadata - boolean - optional - default: true
## Deprecated: [v0.49.0] Use `host_metadata::hostname_source` instead.
## This option will be removed in v0.52.0.
#
# use_resource_metadata: true
## @param only_metadata - boolean - optional - default: false
## Whether to send only metadata. This is useful for agent-collector
## setups, so that metadata about a host is sent to the backend even
## when telemetry data is reported via a different host.
#
# only_metadata: false
## @param api - custom object - required.
## Specific API configuration.
#
api:
## @ param key - string - required
## The Datadog API key to associate your Agent's data with your organization.
## Create a new API key here: https://app.datadoghq.com/account/settings
## If unset it will be determined from the `DD_API_KEY` environment variable (Deprecated: [v0.47.0] set environment variable explicitly on configuration instead).
#
key: "<YOUR API KEY>"
## @param site - string - optional - default: datadoghq.com
## The site of the Datadog intake to send Agent data to.
## Set to 'datadoghq.eu' to send data to the EU site.
## If unset it will be determined from the `DD_SITE` environment variable (Deprecated: [v0.47.0] set environment variable explicitly on configuration instead).
#
# site: datadoghq.com
## @param fail_on_invalid_key - boolean - optional - default: false
## Whether to exit at startup on invalid API key.
#
# fail_on_invalid_key: false
## @param tls - custom object - optional
# TLS settings for HTTPS communications.
# tls:
## @param tls - boolean - optional - default: false
# insecure_skip_verify: false
## @param metrics - custom object - optional
## Metric exporter specific configuration.
#
# metrics:
## @param send_monotonic_counter - boolean - optional - default: true
## Deprecated: [v0.48.0] Use `metrics::sums::cumulative_monotonic_mode` instead.
## Whether to report monotonic metrics as counters or gauges (raw value).
## See https://docs.datadoghq.com/integrations/guide/prometheus-metrics/#counter
## for further details
#
# send_monotonic_counter: true
## @param report_quantiles - boolean - optional - default: true
## Deprecated: [v0.50.0] Use `metrics::summaries::mode` instead.
## Whether to report quantiles for summary metrics.
#
# report_quantiles: true
## @param - delta_ttl - integer - optional - default: 3600
## The amount of time (in seconds) that values are kept in memory for
## calculating deltas for cumulative monotonic metrics.
#
# delta_ttl: 3600
## @param endpoint - string - optional
## The host of the Datadog intake server to send metrics to.
## If unset it will be determined from the `DD_URL` environment variable (Deprecated: [v0.47.0] set environment variable explicitly on configuration instead).
## If both this and `DD_URL` are unset, the value is obtained through the `site` parameter in the `api` section.
#
# endpoint: https://api.datadoghq.com
## @param resource_attributes_as_tags - string - optional - default: false
## Set to true to add all resource attributes of a metric to its metric tags.
## When set to false, only a small predefined subset of resource attributes is converted
## to metric tags.
#
# resource_attributes_as_tags: false
## Deprecated: [0.54.0] use instrumentation_scope_metadata_as_tags instead in favor of
## https://github.com/open-telemetry/opentelemetry-proto/releases/tag/v0.15.0
## Both must not be enabled at the same time.
## @param instrumentation_library_metadata_as_tags - string - optional - default: false
## Set to true to add metadata about the instrumentation library that created a metric.
#
# instrumentation_library_metadata_as_tags: false
## @param instrumentation_scope_metadata_as_tags - string - optional - default: false
## Set to true to add metadata about the instrumentation scope that created a metric.
#
# instrumentation_scope_metadata_as_tags: false
## @param histograms - custom object - optional
## Histograms specific configuration.
## @param mode - string - optional - default: distributions
## How to report histograms. Valid values are:
##
## - `distributions` to report metrics as Datadog distributions (recommended).
## - `nobuckets` to not report bucket metrics,
## - `counters` to report one metric per histogram bucket.
#
# mode: distributions
## @param send_count_sum_metrics - boolean - optional - default: false
## Whether to report sum and count as separate histogram metrics.
#
# send_count_sum_metrics: false
## @param sums - custom object - optional
## Sums specific configuration.
## @param cumulative_monotonic_mode - string - optional - default: to_delta
## How to report cumulative monotonic sums. Valid values are:
##
## - `to_delta` to calculate delta for sum in the client side and report as Datadog counts.
## - `raw_value` to report the raw value as a Datadog gauge.
#
# cumulative_monotonic_mode: to_delta
## @param summaries - custom object - optional
## Summaries specific configuration.
## @param mode - string - optional - default: gauges
## How to report summaries. Valid values are:
##
## - `noquantiles` to not report quantile metrics
## - `gauges` to report one gauge metric per quantile.
#
# mode: gauges
## @param traces - custom object - optional
## Trace exporter specific configuration.
#
# traces:
## @param endpoint - string - optional
## The host of the Datadog intake server to send traces to.
## If unset it will be determined from the `DD_APM_URL` environment variable (Deprecated: [v0.47.0] set environment variable explicitly on configuration instead).
## If both this and `DD_APM_URL` are unset, the value is obtained through the `site` parameter in the `api` section.
#
# endpoint: https://api.datadoghq.com
## @param ignore_resources - list of strings - optional
## A blacklist of regular expressions can be provided to disable certain traces based on their resource name
## all entries must be surrounded by double quotes and separated by commas.
#
# ignore_resources: ["(GET|POST) /healthcheck"]
## @param span_name_remappings - map of key/value pairs - optional
## A map of Datadog span operation name keys and preferred name valuues to update those names to. This can be used to
## automatically map Datadog Span Operation Names to an updated value, and is useful when a user wants to
## shorten or modify span names to something more user friendly in the case of instrumentation libraries with
## particularly verbose names.
#
# span_name_remappings:
# io.opentelemetry.javaagent.spring.client: spring.client
# instrumentation:express.server: express
# go.opentelemetry.io_contrib_instrumentation_net_http_otelhttp.client: http.client
## @param span_name_as_resource_name - use OpenTelemetry semantic convention for span naming - optional
## Option created to maintain similarity with the OpenTelemetry semantic conventions as discussed in the issue below.
## https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions
## https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/1909
#
# span_name_as_resource_name: true
## @param host_metadata - custom object - optional
## Host metadata specific configuration.
## Host metadata is the information used for populating the infrastructure list, the host map and providing host tags functionality within the Datadog app.
##
## The exporter will only send host metadata for a single host, whose name is chosen
## according to `host_metadata::hostname_source`.
#
# host_metadata:
## @param enabled - boolean - optional - default: true
## Enable the host metadata functionality
#
# enabled: true
## @param hostname_source - enum - optional - default: first_resource
## Source for the hostname of host metadata.
## Valid values are 'first_resource' and 'config_or_system':
## - 'first_resource' picks the host metadata hostname from the resource attributes on the first OTLP payload that gets to the exporter.
## If the first payload lacks hostname-like attributes, it will fallback to 'config_or_system' behavior.
## Do not use this hostname source if receiving data from multiple hosts.
##
## - 'config_or_system' picks the host metadata hostname from the 'hostname' setting, falling back to system and cloud provider APIs.
##
## The current default is 'first_resource'.
#
# hostname_source: first_resource
## @param tags - list of strings - optional - default: empty list
## List of host tags to be sent as part of the host metadata.
## These tags will be attached to telemetry signals that have the host metadata hostname.
##
## To attach tags to telemetry signals regardless of the host, use a processor instead.
#
# tags: []
service:
pipelines:
traces:
receivers: [nop]
processors: [nop]
exporters: [datadog]