Datadog
Datadog distribution is live: it reuses the same canonical score payload already used for Cortex/OpsLevel/Backstage, submitted as Datadog custom gauge metrics (vibgrate.drift_score, vibgrate.eol_count, and — once computed — vibgrate.risk_score, vibgrate.drift_risk) tagged by service — it is not a general monitoring or APM integration.
What's live today
Datadog connections submit vibgrate.drift_score and vibgrate.eol_count as gauge metrics via the Datadog Metrics API immediately after a scan, tagged service, risk_level, and trend so they join existing Datadog service dashboards. vibgrate.risk_score and vibgrate.drift_risk are submitted in a second push once the SCA pipeline computes RiskScore for that scan — the gauge simply isn't submitted (not sent as 0) until then. A Score types setting per connection (DriftScore only / DriftRisk only / both) controls which metrics a connection ever receives — a DriftScore-only connection never gets a vibgrate.risk_score submission at all. Pushes run automatically after a scan and on demand via a manual sync, gated by the integrations:write permission and logged to the delivery log like every other connection. This is a metric push only — not a general monitoring, APM, or log-ingestion integration.