devops:monitoring:datadog:metricseventstags
This is an old revision of the document!
Table of Contents
Pregunta 1
What is the purpose of aggregating events?
- To create monitors
- To combine similar events together
- To define SLOs
- To store event data
Pregunta 2
What environment variable extracts Docker container labels as tags?
- DD_TAG_IMPORTER
- DD_CONTAINER_TAGS
- DD_DOCKER_LABELS_AS_TAGS
- DD_DOCKER_TAG_EXTRACTOR
Pregunta 3
What happens to metric data values during the flush time interval?
- They are collected by Datadog and processed based on metric type
- They are sent to a backup data store
- They are deleted
- They are encrypted
Pregunta 4
What can full-text search of events be used for?
- Finding events containing specific keywords
- Calculating aggregates
- Creating monitors
- Defining metrics
Pregunta 5
Which default integration monitors system CPU metrics?
- Directory
- Network
- System
- Process
Pregunta 6
What best practice is used to partition large volumes of metric data?
- Modifying the agent configuration
- Adding custom tags from integrations
- Upgrading to enterprise support
- Deleting old metrics
Pregunta 7
How can events be classified in Datadog?
- By type, host, value
- By source, priority, severity/status
- By ID, name
- By timestamp, interval, unit
devops/monitoring/datadog/metricseventstags.1739535066.txt.gz · Last modified: 2025/02/14 12:11 by 85.219.17.206