ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #datadog
Learn how to choose between rate-based and priority-based trace sampling in Datadog APM to reduce ingestion costs without losing critical error data.
Choose the right Datadog Agent deployment in Kubernetes—DaemonSet, sidecar, or host process—by comparing coverage, resources, and security. Follow a concrete DaemonSet example and verification steps to ensure reliable monitoring.
Learn how to embed Datadog trace IDs in your application logs so you can jump from a log entry to its corresponding trace with one click, and understand the trade‑offs involved.
A concise architecture note for Datadog APM tracing: requirements, minimal single‑Agent design, trust boundaries, operational checks, failure modes, and when to redesign.
Datadog Agent rollback does not guarantee preservation of configuration files that were modified after the last successful upgrade. The rollback command requires the 'Datadog Agent: Manage' permission, yet it is unclear whether this permission covers scenarios where the previous agent version is not cached locally, and a file lock left unreleased by a crash
Public Dashboard Sharing Datadog allows the generation of public URLs to share dashboards with external stakeholders without requiring authentication. This feature is designed for high-level visibility, but it lacks native technical guardrails to prevent persistent exposure of operational data. Access Constraints Current implementation allows any user with t
Log Deduplication via API v2 The Datadog Agent (version 7.30 and later) introduces the use_idempotency_key configuration within logs_config . When enabled, the Agent attaches an Idempotency-Key header to requests sent to the /api/v2/logs endpoint to prevent duplicate entries during transient network failures. Persistence Constraints While this mechanism hand
The goal is to understand the upper bound of latency between the completion of a Datadog Logs rehydration job and the moment the rehydrated logs become searchable in the platform. Datadog documents that rehydrated logs become searchable after the job finishes, but the exact latency is not guaranteed and can vary with backend load, data volume, and the number
When configuring a Datadog integration check, administrators may define the same parameter in both the main datadog.yaml file and the check‑specific file under conf.d/.yaml . The goal is to determine which value the Agent actually applies at runtime in Agent 7.x, especially when the dual‑stack migration mode is enabled and the autopilot feature may be managi
kubernetes