✦ Sample Prompt
Add standardized Datadog monitoring configuration to all services.
For each repository:
1. Add or update datadog.yaml configuration:
- Set service name tag matching the repository/service name
- Set env tag based on deployment environment detection
- Enable APM tracing with default sample rate of 1.0
- Enable log collection and correlation with traces
2. Add Kubernetes pod annotations for Datadog auto-discovery:
ad.datadoghq.com/<container>.logs: '[{"service":"<service-name>","source":"<language>"}]'
3. Add a /health endpoint check configuration if not present
4. Ensure consistent tagging: service, env, version across all config files
If the service already has Datadog configuration, merge missing settings
without overwriting existing customizations.The Problem
Observability only works when every service is instrumented. When teams onboard monitoring individually, configuration drifts: some services report to Datadog, others don't. Tags are inconsistent. Health check endpoints exist in some services but not others. When an incident happens, the gaps in monitoring coverage are the first thing that hurts you.
Rolling out consistent monitoring config (standard tags, sampling rates, health checks, log correlation) is a classic "important but not urgent" task that never gets prioritized until after an outage.
What Tidra Does
- Scans each repository for existing monitoring configuration (Datadog, OTEL, Prometheus)
- Adds or updates configuration files with the standardized settings, merging with existing configs where present
- Adds Kubernetes annotations for auto-discovery if deployment manifests exist
- Creates PRs detailing what monitoring configuration was added or updated
Before & After
diff
k8s/deployment.yaml
metadata:
name: payments-service
+ annotations:
+ ad.datadoghq.com/payments-service.logs: >-
+ [{"service":"payments-service","source":"nodejs"}]
+ ad.datadoghq.com/payments-service.tags: >-
+ '{"team":"payments","tier":"critical"}'
spec:
containers:
- name: payments-service
+ env:
+ - name: DD_SERVICE
+ value: "payments-service"
+ - name: DD_ENV
+ valueFrom:
+ fieldRef:
+ fieldPath: metadata.labels['env']
Customization Tips
- OpenTelemetry: Replace the Datadog-specific configuration with OTEL collector config if your org is migrating to vendor-neutral observability.
- Sample rates: Adjust the APM sample rate based on traffic volume. High-traffic services may need a lower rate (e.g., 0.1) to control costs.
- Custom tags: Add team, cost-center, or business-unit tags based on your organization's tagging taxonomy.