-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Expand file tree
/
Copy pathprocess_config.yaml
More file actions
428 lines (425 loc) · 13 KB
/
Copy pathprocess_config.yaml
File metadata and controls
428 lines (425 loc) · 13 KB
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
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
$schema: https://json-schema.org/draft/2020-12/schema
$id: https://raw.githubusercontent.com/DataDog/datadog-agent/main/pkg/config/schema/yaml/process_config.yaml
node_type: section
title: Process Collection Configuration
type: object
visibility: public
description: |-
Enter specific configurations for your Process data collection.
Uncomment this parameter and the one below to enable them.
See https://docs.datadoghq.com/graphing/infrastructure/process/
tags:
- template_section:CoreAgent
- full-agent-only:true
properties:
process_collection:
node_type: section
type: object
visibility: public
description: Specifies settings for collecting processes.
tags:
- template_section:CoreAgent
properties:
enabled:
node_type: setting
type: boolean
default: false
env_vars:
- DD_PROCESS_CONFIG_PROCESS_COLLECTION_ENABLED
- DD_PROCESS_AGENT_PROCESS_COLLECTION_ENABLED
visibility: public
description: Enables collection of information about running processes.
container_collection:
node_type: section
type: object
visibility: public
description: Specifies settings for collecting containers.
tags:
- template_section:CoreAgent
properties:
enabled:
node_type: setting
type: boolean
default: true
env_vars:
- DD_PROCESS_CONFIG_CONTAINER_COLLECTION_ENABLED
- DD_PROCESS_AGENT_CONTAINER_COLLECTION_ENABLED
visibility: public
description: Enables collection of information about running containers.
expvar_port:
node_type: setting
type: integer
default: 6062
env_vars:
- DD_PROCESS_CONFIG_EXPVAR_PORT
- DD_PROCESS_AGENT_EXPVAR_PORT
visibility: public
description: Port for the debug endpoints for the process Agent.
cmd_port:
node_type: setting
type: integer
default: 6162
env_vars:
- DD_PROCESS_CONFIG_CMD_PORT
- DD_PROCESS_AGENT_CMD_PORT
visibility: public
description: Port for configuring runtime settings for the process Agent.
log_file:
node_type: setting
type: string
default: ${log_path}/process-agent.log
env_vars:
- DD_PROCESS_CONFIG_LOG_FILE
- DD_PROCESS_AGENT_LOG_FILE
visibility: public
description: The full path to the file where process Agent logs are written.
intervals:
node_type: section
type: object
visibility: public
description: |-
The interval, in seconds, at which the Agent runs each check. If you want consistent
behavior between real-time, set the `container_realtime` and `process_realtime` intervals to 10.
tags:
- template_section:CoreAgent
properties:
container:
node_type: setting
type: integer
default: 10
env_vars:
- DD_PROCESS_CONFIG_INTERVALS_CONTAINER
- DD_PROCESS_AGENT_INTERVALS_CONTAINER
visibility: public
description: The interval in seconds at which the container check runs.
container_realtime:
node_type: setting
type: integer
default: 2
env_vars:
- DD_PROCESS_CONFIG_INTERVALS_CONTAINER_REALTIME
- DD_PROCESS_AGENT_INTERVALS_CONTAINER_REALTIME
visibility: public
description: The interval in seconds at which the real-time container check
runs.
process:
node_type: setting
type: integer
default: 10
env_vars:
- DD_PROCESS_CONFIG_INTERVALS_PROCESS
- DD_PROCESS_AGENT_INTERVALS_PROCESS
visibility: public
description: The interval in seconds at which the process check runs.
comment: |-
The interval, in seconds, at which we will run each check. If you want consistent
behavior between real-time you may set the Container/ProcessRT intervals to 10.
Defaults to 10s for normal checks and 2s for others.
process_realtime:
node_type: setting
type: integer
default: 2
env_vars:
- DD_PROCESS_CONFIG_INTERVALS_PROCESS_REALTIME
- DD_PROCESS_AGENT_INTERVALS_PROCESS_REALTIME
visibility: public
description: The interval in seconds at which the real-time process check
runs.
connections:
node_type: setting
type: integer
default: 30
env_vars:
- DD_PROCESS_CONFIG_INTERVALS_CONNECTIONS
- DD_PROCESS_AGENT_INTERVALS_CONNECTIONS
process_discovery:
node_type: section
type: object
visibility: public
description: Specifies custom settings for the `process_discovery` object.
tags:
- template_section:CoreAgent
properties:
enabled:
node_type: setting
type: boolean
default: true
env_vars:
- DD_PROCESS_CONFIG_PROCESS_DISCOVERY_ENABLED
- DD_PROCESS_AGENT_PROCESS_DISCOVERY_ENABLED
- DD_PROCESS_CONFIG_DISCOVERY_ENABLED
- DD_PROCESS_AGENT_DISCOVERY_ENABLED
visibility: public
description: Toggles the `process_discovery` check. If enabled, this check
gathers information about running integrations.
interval:
node_type: setting
type: string
default: 4h0m0s
env_vars:
- DD_PROCESS_CONFIG_PROCESS_DISCOVERY_INTERVAL
- DD_PROCESS_AGENT_PROCESS_DISCOVERY_INTERVAL
format: duration
visibility: public
description: An interval in hours that specifies how often the process discovery
check should run (minimum is 10min).
example: 4h
tags:
- golang_type:duration
hint_frequency:
node_type: setting
type: integer
default: 60
env_vars:
- DD_PROCESS_CONFIG_PROCESS_DISCOVERY_HINT_FREQUENCY
- DD_PROCESS_AGENT_PROCESS_DISCOVERY_HINT_FREQUENCY
blacklist_patterns:
node_type: setting
type: array
default: []
env_vars:
- DD_PROCESS_CONFIG_BLACKLIST_PATTERNS
- DD_PROCESS_AGENT_BLACKLIST_PATTERNS
items:
type: string
visibility: public
description: A list of regex patterns that exclude processes if matched.
example: |2-
- <REGEX>
queue_size:
node_type: setting
type: integer
default: 256
env_vars:
- DD_PROCESS_CONFIG_QUEUE_SIZE
- DD_PROCESS_AGENT_QUEUE_SIZE
visibility: public
description: The number of check results to buffer in memory when a POST fails.
process_queue_bytes:
node_type: setting
type: integer
default: 60000000
env_vars:
- DD_PROCESS_CONFIG_PROCESS_QUEUE_BYTES
- DD_PROCESS_AGENT_PROCESS_QUEUE_BYTES
visibility: public
description: The amount of data (in bytes) to buffer in memory when a POST fails.
rt_queue_size:
node_type: setting
type: integer
default: 5
env_vars:
- DD_PROCESS_CONFIG_RT_QUEUE_SIZE
- DD_PROCESS_AGENT_RT_QUEUE_SIZE
visibility: public
description: The number of realtime check results to buffer in memory when a POST
fails.
max_per_message:
node_type: setting
type: integer
default: 100
env_vars:
- DD_PROCESS_CONFIG_MAX_PER_MESSAGE
- DD_PROCESS_AGENT_MAX_PER_MESSAGE
visibility: public
description: The maximum number of processes or containers per message.
dd_agent_bin:
node_type: setting
type: string
env_vars:
- DD_PROCESS_CONFIG_DD_AGENT_BIN
- DD_PROCESS_AGENT_DD_AGENT_BIN
visibility: public
description: |-
Overrides the path to the Agent bin used for getting the hostname. Defaults are:
* Windows: <AGENT_DIRECTORY>\\embedded\\agent.exe
* Unix: /opt/datadog-agent/bin/agent/agent
platform_default:
linux: ${install_path}/bin/agent/agent
darwin: ${install_path}/bin/agent/agent
aix: ${install_path}/bin/agent/agent
windows: ${install_path}/bin/agent.exe
dd_agent_env:
node_type: setting
type: string
default: ''
env_vars:
- DD_PROCESS_CONFIG_DD_AGENT_ENV
- DD_PROCESS_AGENT_DD_AGENT_ENV
visibility: public
description: Overrides of the environment we pass to fetch the hostname.
scrub_args:
node_type: setting
type: boolean
default: true
env_vars:
- DD_SCRUB_ARGS
- DD_PROCESS_CONFIG_SCRUB_ARGS
- DD_PROCESS_AGENT_SCRUB_ARGS
visibility: public
description: Hide sensitive data on the Live Processes page.
custom_sensitive_words:
node_type: setting
type: array
default: []
env_vars:
- DD_CUSTOM_SENSITIVE_WORDS
- DD_PROCESS_CONFIG_CUSTOM_SENSITIVE_WORDS
- DD_PROCESS_AGENT_CUSTOM_SENSITIVE_WORDS
items:
type: string
visibility: public
description: |-
Define your own list of sensitive data to be merged with the default one.
Read more on Datadog documentation:
https://docs.datadoghq.com/graphing/infrastructure/process/#process-arguments-scrubbing
example: |2-
- 'personal_key'
- '*token'
- 'sql*'
- '*pass*d*'
env_parser: json_list_or_comma_separated
disable_realtime_checks:
node_type: setting
type: boolean
default: false
env_vars:
- DD_PROCESS_CONFIG_DISABLE_REALTIME_CHECKS
- DD_PROCESS_AGENT_DISABLE_REALTIME_CHECKS
visibility: public
description: Disable realtime process and container checks
additional_endpoints:
node_type: setting
type: object
default: {}
env_vars:
- DD_PROCESS_CONFIG_ADDITIONAL_ENDPOINTS
- DD_PROCESS_AGENT_ADDITIONAL_ENDPOINTS
- DD_PROCESS_ADDITIONAL_ENDPOINTS
additionalProperties:
items:
type: string
type: array
cache_lookupid:
node_type: setting
type: boolean
default: false
env_vars:
- DD_PROCESS_CONFIG_CACHE_LOOKUPID
- DD_PROCESS_AGENT_CACHE_LOOKUPID
drop_check_payloads:
node_type: setting
type: array
default: []
env_vars:
- DD_PROCESS_CONFIG_DROP_CHECK_PAYLOADS
- DD_PROCESS_AGENT_DROP_CHECK_PAYLOADS
items:
type: string
enabled:
node_type: setting
type: string
default: 'false'
env_vars:
- DD_PROCESS_CONFIG_ENABLED
- DD_PROCESS_AGENT_ENABLED
comment: |-
Env bindings below are mirrored in pkg/procmgr/rust/src/config_gate/env_bindings.rs.
"process_config.enabled" is deprecated. We must still be able to detect if it is present, to know if we should use it
or container_collection.enabled and process_collection.enabled.
It's a string as the possible values are "disabled", "false", "true"...
grpc_connection_timeout_secs:
node_type: setting
type: integer
default: 60
env_vars:
- DD_PROCESS_CONFIG_GRPC_CONNECTION_TIMEOUT_SECS
- DD_PROCESS_AGENT_GRPC_CONNECTION_TIMEOUT_SECS
ignore_zombie_processes:
node_type: setting
type: boolean
default: false
env_vars:
- DD_PROCESS_CONFIG_IGNORE_ZOMBIE_PROCESSES
- DD_PROCESS_AGENT_IGNORE_ZOMBIE_PROCESSES
internal_profiling:
node_type: section
type: object
properties:
enabled:
node_type: setting
type: boolean
default: false
env_vars:
- DD_PROCESS_CONFIG_INTERNAL_PROFILING_ENABLED
- DD_PROCESS_AGENT_INTERNAL_PROFILING_ENABLED
language_detection:
node_type: section
type: object
properties:
grpc_port:
node_type: setting
type: integer
default: 6262
env_vars:
- DD_PROCESS_CONFIG_LANGUAGE_DETECTION_GRPC_PORT
- DD_PROCESS_AGENT_LANGUAGE_DETECTION_GRPC_PORT
max_message_bytes:
node_type: setting
type: integer
default: 1000000
env_vars:
- DD_PROCESS_CONFIG_MAX_MESSAGE_BYTES
- DD_PROCESS_AGENT_MAX_MESSAGE_BYTES
orchestrator_additional_endpoints:
node_type: setting
type: object
default: {}
additionalProperties:
items:
type: string
type: array
tags:
- no-env
comment: DEPRECATED in favor of `orchestrator_explorer.orchestrator_additional_endpoints`
setting. If both are set `orchestrator_explorer.orchestrator_additional_endpoints`
will take precedence.
orchestrator_dd_url:
node_type: setting
type: string
default: ''
env_vars:
- DD_PROCESS_CONFIG_ORCHESTRATOR_DD_URL
- DD_PROCESS_AGENT_ORCHESTRATOR_DD_URL
comment: DEPRECATED in favor of `orchestrator_explorer.orchestrator_dd_url` setting.
If both are set `orchestrator_explorer.orchestrator_dd_url` will take precedence.
process_dd_url:
node_type: setting
type: string
default: ''
env_vars:
- DD_PROCESS_CONFIG_PROCESS_DD_URL
- DD_PROCESS_AGENT_PROCESS_DD_URL
- DD_PROCESS_AGENT_URL
- DD_PROCESS_CONFIG_URL
strip_proc_arguments:
node_type: setting
type: boolean
default: false
env_vars:
- DD_STRIP_PROCESS_ARGS
- DD_PROCESS_CONFIG_STRIP_PROC_ARGUMENTS
- DD_PROCESS_AGENT_STRIP_PROC_ARGUMENTS
windows:
node_type: section
type: object
properties:
use_perf_counters:
node_type: setting
type: boolean
default: false
env_vars:
- DD_PROCESS_CONFIG_WINDOWS_USE_PERF_COUNTERS
- DD_PROCESS_AGENT_WINDOWS_USE_PERF_COUNTERS
comment: Use PDH API to collect performance counter data for process check
on Windows