Datadog Fundamentals flashcards
Datadog Fundamentals · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- DogStatsD
- A statsd-compatible service bundled with the Datadog Agent that accepts custom metrics, events, and service checks over UDP from applications.
- Distribution metric
- A Datadog metric type that aggregates raw values across all hosts before computing global percentiles, unlike histograms which aggregate per host.
- Autodiscovery
- An Agent capability that applies integration check configurations from container labels or Kubernetes annotations, avoiding manual edits to Agent configuration files.
- Unified service tagging
- Applying the three reserved tags env, service, and version to telemetry so Datadog correlates metrics, traces, logs, and deployments across products.
- COUNT metric type
- A submission type where the Agent reports how many occurrences happened during the flush interval; Datadog divides by the interval to display a rate.
- Downtime
- A scheduled mute applied to monitors by tag scope, either one-time or recurring, that suppresses notifications without deleting the monitor.
- Span
- A single timed operation within a trace, carrying a span ID, parent ID, service, resource, operation name, duration, and tags.
- Trace
- A distributed set of spans sharing one trace ID that represents the complete path of a request as it moves across services.
- Apdex
- An application performance score using a target time T, computed as satisfied requests plus half the tolerating requests, divided by total requests.
- Continuous Profiler
- An APM feature that samples code-level CPU, memory, and lock usage in production to identify hot code paths without extra instrumentation.
- Retention filter
- An APM setting that decides which spans are indexed and therefore searchable in the Trace Explorer, controlling indexing cost and query coverage.
- Service dependency map
- An APM visualization of upstream and downstream services, showing request rate, error rate, and latency for each connection edge.
- Log pipeline
- An ordered set of processors that parse, enrich, and normalize logs before they reach indexes, including grok parsers, remappers, and category processors.
- Grok parser
- A log processor that extracts structured attributes from unstructured text using named patterns such as %{TIMESTAMP_ISO8601:timestamp}.
- Exclusion filter
- A per-index log filter that drops matching logs before indexing while still allowing them to be counted and used for log-based metrics.
- Log-based metric
- A custom metric generated from log events by counting occurrences or distributing a numeric attribute across a query, reusable in dashboards and monitors.
- Log archive
- A long-term storage destination such as S3, GCS, or Azure Blob where logs are forwarded after indexing and can later be rehydrated.
- RUM view
- A user-facing page or screen in Real User Monitoring that groups the actions, errors, resources, and timings recorded during one visit.
- Session replay
- A RUM feature that records browser interactions and DOM changes so you can replay a user session alongside its errors and traces.
- Synthetic API test
- A test that sends single or chained HTTP requests from selected locations and asserts on status, headers, body, and response time.
- Private location
- A synthetic monitoring worker deployed inside your own network so tests can reach internal endpoints that are not exposed to the public internet.
- Core Web Vitals
- User-experience metrics reported by RUM browser SDKs covering loading (LCP), interactivity (INP or FID), and visual stability (CLS).
- Cloud SIEM
- A Datadog security product that analyzes ingested logs with detection rules to produce prioritized threat signals for investigation.
- CSM Threats
- A workload security capability that uses Agent probes to detect and block suspicious process, file, and network activity on hosts and containers.
- Application Security Management
- A Datadog product that uses the tracing library inside running services to detect attacks and code-level vulnerabilities and raise security signals.
- Sensitive Data Scanner
- A Datadog feature that matches patterns to detect and optionally redact PII or secrets in logs, traces, RUM events, and other events.
- Security signal
- An alert generated by a security detection rule that carries severity, the rule name, affected resources, and a timeline for investigation.
- API key
- An organization-level Datadog key used by the Agent and integrations to submit data; it cannot be used to read data through APIs.
- Application key
- A user-level or service-account key required for programmatic read and write access to Datadog APIs, bounded by that identity's permissions.
- Composite monitor
- A monitor that combines several underlying monitors with boolean logic and triggers only when the combined expression evaluates to true.
- Incident severity
- A configurable level, defaulting to SEV-1 through SEV-5, assigned to an incident that determines notifications and escalation expectations.
- Service Catalog
- A Datadog registry of services holding ownership, metadata, and links to APM, dashboards, and on-call for ownership and maturity tracking.