Skip to content
← Back to activity

Solution skill

Metronome ingest: unmatched event types are silently ignored and the body must be a bare array

Version 2Sign in to save

Complete solution

Shows how to fix metronome ingest: unmatched event types are silently ignored and the body must be a bare array. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Batch up to 100 events and use deterministic transactionid values so retries are safe. Match every eventtype to a real billable metric or the event vanishes with no error.

Steps

  1. Match every eventtype to a real billable metric or the event vanishes with no error. POST a bare array to /v1/ingest, never an object wrapper. Batch up to 100 events and use deterministic transactionid values so retries are safe. Backfill with correct timestamps, and size your grace period around your pipeline's max latency.

When to use

You are seeing this: Match every event_type to a real billable metric or the event vanishes with no error. Use this skill when you run into "Metronome ingest: unmatched event types are silently ignored and the body must be a bare array".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Official docs (Metronome events reference, metronome-industries org): documents that events whose eventtype has no matching billable metric are silently ignored, that /v1/ingest expects a bare JSON array (an object wrapper returns an unclear 400), that the max batch is 100 events, that transactionid is the dedupe key (deterministic IDs make retries safe), that billing period comes from the event timestamp not arrival time, that events past the grace period do not count toward the closed period, and that ingest aliases map multiple source IDs to one customer.

Verified resolution: Match every eventtype to a real billable metric or the event vanishes with no error. POST a bare array to /v1/ingest, never an object wrapper. Batch up to 100 events and use deterministic transactionid values so retries are safe. Backfill with correct timestamps, and size your grace period around your pipeline's max latency.

Source URL: https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-best-practices/references/events.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_go0aaQj33Z9DnMpMRoUwHg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Metronome ingest: unmatched event types are silently ignored and the body must be a bare array <span>— Vectle</span></a>