Meter Health

Meter Health monitors the continuity and reliability of event ingestion across your Stripe billing meters. It surfaces gaps, anomalies, and silence periods so you can catch billing data issues before they affect invoices.

Health signals

Each meter is assigned a health status based on observed ingestion patterns:

Status	Meaning
Healthy	Events arriving as expected with no detected gaps or anomalies
Warning	Reduced event volume or a short ingestion gap — worth investigating
No events	No events ingested for a period longer than expected based on history
New	Meter was recently created and does not yet have an established baseline

Gap detection

A gap is a period with no meter events where events were expected based on prior ingestion history. MeterMonitor flags a gap when:

A meter with consistent daily events has no events for 24 hours or more.

Event volume drops more than 80% compared to the same period in the prior week.

A meter that had events in the current billing period stops receiving events mid-period.

Note

Gap detection uses each meter’s own historical baseline, not a fixed threshold. A meter that ingests events sporadically will have a wider tolerance than one that ingests every hour.

Anomaly signals

In addition to gaps, Meter Health surfaces:

Volume spike — event count significantly exceeds the normal range for the period.

Volume drop — event count is significantly below the normal range.

Duplicate cluster — unusually high proportion of events share the same idempotency key, customer, and timestamp combination.

Meter detail view

Clicking a meter opens its detail view, which shows:

Event volume chart for the last 30 days.

Health status history.

Recent gaps or anomalies with timestamps.

Top customers contributing events.

Last event received.

Acting on health issues

If a meter shows a gap or warning:

Check whether your integration is still sending events to Stripe for that meter.

Review recent Stripe webhook logs or API call logs for errors.

Verify the meter's event_name matches what your integration is reporting.

Use the meter detail view to identify the exact time events stopped.

Tip

If a meter legitimately has no events because your users are not active, MeterMonitor will still flag it as no-events. You can dismiss the signal from the meter detail view to suppress it for that period.