## TL;DR

Set DO\_NOT\_TRACK=1 in the Inngest server's environment. The same error from your app usually means INNGEST\_EVENT\_KEY is not set on both the server and your SDK.

## Steps

1. 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.

2. 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.

## When to use

You are seeing this: Self-hosted Inngest (docker compose, inngest start) with INNGEST\_EVENT\_KEY and INNGEST\_SIGNING\_KEY set. Use this skill when you run into "Self-hosted Inngest logs flooded with "rejecting event; event key not recognized"".

## 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

This flood is the Inngest server's own usage telemetry, not your app.
