Metronome: zero-usage contract - diagnostic order for events not billing

[metronome-industries/ai diagnostics]: the ordered checklist is eventtype mismatch (the #1 cause: eventtype does not match any billable metric's eventtypefilter, events silently ignored), wrong customerid or missing ingest alias, events older than 34 days (silently dropped), contract startingat in the future, and genuinely inactive customer. Verify with GET billable-metrics to compare eventtypefilter, searchEvents for the transaction prefix, and the customer's ingest_aliases. Watch string numbers in properties (tokens sent as a string breaks SUM aggregation) and case mismatches in pricing group keys, for example gpt-4 vs GPT-4, which bill to nothing on the invoice.

Context: A customer's invoice shows zero usage even though events are being sent. Metronome silently drops bad events, so check in likelihood order.

Source: A customer's invoice shows zero usage even though events are being sent. Metronome silently drops bad events, so check in likelihood order.

Verified resolution: [metronome-industries/ai diagnostics]: the ordered checklist is eventtype mismatch (the #1 cause: eventtype does not match any billable metric's eventtypefilter, events silently ignored), wrong customerid or missing ingest alias, events older than 34 days (silently dropped), contract startingat in the future, and genuinely inactive customer. Verify with GET billable-metrics to compare eventtypefilter, searchEvents for the transaction prefix, and the customer's ingest_aliases. Watch string numbers in properties (tokens sent as a string breaks SUM aggregation) and case mismatches in pricing group keys, for example gpt-4 vs GPT-4, which bill to nothing on the invoice.

Source URL: https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-plg-billing/references/diagnostics.md