---
name: Monitoring Base - mql-enrichment-service
description: Shared dashboard suite covering health, cost, quality, and drift across all three L5 platforms. {{observability_platform}} board id revops-mql-pipeline-001. Owner: RevOps-Ops.
type: cross-platform-artifact
layer: L7-concern
Owner: RevOps-Ops
---

# Monitoring Base - mql-enrichment-service

- **Last reviewed:** 2026-04-27 (oncall shift-start check)
- **Review cadence:** quarterly + on schema bump in upstream telemetry
- **Status:** exists-mature

## What this means here

A shared dashboard suite covering health, cost, quality, and drift across every L5 platform. Without monitoring base, each platform would have its own dashboard; cross-platform issues (e.g., mirror drift affecting all three platforms simultaneously) would be invisible until they surfaced as user-facing degradation.

## Implementation

- **Platform:** {{observability_platform}}
- **Board id:** `revops-mql-pipeline-001`
- **Dashboard URL:** `{{observability_platform}}.{{cutting_edge_saas_company}}.com/d/revops-mql-pipeline-001`
- **Data source:** {{observability_platform}} ingests from `revops-ai-mql-enrichment` log group (per L3 telemetry schema)
- **Refresh cadence:** real-time for active panels; 5-minute for cost rollups

## Panel structure

Four panel groups:

### Group 1: Health
- Per-platform p50, p95, p99 latency
- Success rate, error rate
- Per-platform queue depth (mql-enrichment-service inbound, mql-router transition queue)
- Mirror sync freshness (days since last sync of `kit/`)

### Group 2: Cost
- Per-call cost p50, p90, p99 per platform
- Daily total cost vs. budget
- Cost by enrichment tier (1, 2, 3)
- Cost-ceiling breach count (rolling 24h)

### Group 3: Quality
- Eval scores per quarter (faithfulness, fluency, human-pass) trended
- SDR-explicit-feedback rate (thumbs-up vs. thumbs-down)
- SDR-implicit signal: enrichment-tier-3 expand rate
- Guardrail trip rate by layer + tier
- Staleness rate (Red Line 3 trip rate)

### Group 4: Drift
- Intent-signal data freshness (% of records with snapshot < 90 days)
- Consent revocation propagation latency (rolling p99)
- Schema validation failure rate
- Eval dataset coverage drift (whether new market segments need additional examples)

## Participants

All three platforms feed telemetry into the monitoring base; all three are visible on the dashboard. Cross-platform views (e.g., end-to-end MQL journey latency from enrichment to handoff) live in dedicated panels.

## Oncall posture

Oncall checks the dashboard at every shift start (twice daily; following sun pattern across {{cutting_edge_saas_company}}'s NA / EMEA / APAC regions). Quick checks:

- Any alert firing? (cross-reference with PagerDuty)
- Any panel red? (any threshold breached)
- Any anomaly compared to last 7 days? (visual scan of latency / cost / quality trends)
- Mirror sync freshness? (this is the current open item, 14 days behind)

## Last verified live

2026-04-27 oncall shift-start check; dashboard refreshing within last 2 minutes; all panels rendering correctly. The monitoring base has not had a dashboard outage in this instance's lifetime.

## Inheritance and dependencies

Inherits from: {{cutting_edge_saas_company}} corporate observability platform ({{observability_platform}}).

Consumed by: every L5 dossier; oncall; quarterly review sessions.

## Cross-references inside this instance

- `cross-platform/L7-glue.md`
- `policies/framework-contract.md` (L3) - the telemetry schema feeding this dashboard
- `cross-platform/alerting-fabric.md` - alerts fire when monitoring panels breach thresholds
- `runbooks/oncall-shift-start.md`
