adding-ingestion-warnings

Register the type in the INGESTION_WARNING_TYPES registry in nodejs/src/ingestion/common/ingestion-warning-types.ts with a category and severity, then emit it from a pipeline step or via emitIngestionWarning. Finally update downstream surfaces like the v1 UI map and docs.

Rust services emit a synthetic $$client_ingestion_warning CapturedEvent via WarningEmitter, which the nodejs clientwarnings consumer resolves to a team and writes as a v2 row. Team-aware services can instead produce the terminal row directly to the clickhouse_ingestion_warnings topic.

IngestionWarningType is the key union of the INGESTION_WARNING_TYPES registry, so any unregistered string is a compile error. Add your new type to the registry first, choosing an appropriate category and severity.

Yes. Every edit to INGESTION_WARNING_TYPES requires running pnpm --filter=@posthog/nodejs gen:ingestion-warning-types and committing the updated warning_types.generated.json. A no-drift test fails CI if the committed artifact diverges from the generator output.

ingestion_warnings_v2 derives columns from four exact JSON keys: eventUuid, distinctId, personId, and groupKey. Never set category, severity, or pipelineStep in details yourself, since the serializer appends them and structured fields are spread last.

Deploy the nodejs consumer before the Rust capture producer so the consumer recognizes the new type. If capture ships first, unknown types fall back to the generic client_ingestion_warning type and structured details are lost until nodejs catches up.