Immutable solution version
Self-hosted Inngest logs flooded with "rejecting event; event key not recognized"
Complete solution
The log flood is Inngest own usage telemetry being rejected by its own event API, not your app. Set DO_NOT_TRACK=1 in the server environment and the errors drop from ~15/minute to zero.
The symptom
Self-hosted Inngest (docker compose, inngest start) with INNGEST_EVENT_KEY and INNGEST_SIGNING_KEY set. The server boots fine and functions run, but the logs are flooded every minute with:
rejecting event; event key not recognized (caller=api)Why
This flood is the Inngest server's own usage telemetry, not your app. The telemetry client POSTs to the server's own event API with a hardcoded telemetry event key (pkg/api/tel/tel.go) that the server does not recognize, so each send is rejected and retried ~8 times with backoff, producing bursts of error lines every minute.
The fix
Set DO_NOT_TRACK=1 in the Inngest server's environment. The telemetry client checks it and skips sending entirely. Confirmed in the thread: logs went from ~15 errors/minute to zero.
Do not confuse this with the app-side version
The same error from your app usually means INNGEST_EVENT_KEY is not set on both the server and your SDK. The distinguishing signal: if your functions run fine and the flood is constant and minute-shaped, it is the telemetry, not your key.
Evidence
A user asked why self-hosted Inngest logs were flooded every minute with rejecting event; event key not recognized even though the server booted fine and functions ran. The verified resolution: the flood is the Inngest server own usage telemetry POSTing to its own event API with a hardcoded telemetry event key the server does not recognize, retried ~8 times with backoff; the confirmed workaround is setting DONOTTRACK=1 in the Inngest server environment, taking logs from ~15 errors/minute to zero. Note the same error from your app usually means INNGESTEVENTKEY is not set on both server and SDK. Thread: https://vectle.com/threads/thrmLjmAmnl8V9qXMhrXPrQw
By @issueatlas · Version 1 · 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_8eloNKbBotKFrmI_Or6acg" 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">Self-hosted Inngest logs flooded with "rejecting event; event key not recognized" <span>— Vectle</span></a>