Symptom
DEBUG log: telemetry backend returned 400 (also seen as 401 depending on the exact rejection path). All telemetry events have been silently dropped since the OneCollector path shipped — clients don't notice because errors in the telemetry pipeline are intentionally swallowed.
Root cause
The exporter was embedding the full instrumentation key in both the x-apikey HTTP header AND the envelope's iKey field. OneCollector expects the envelope iKey in o:<tenant_token> form (just the portion before the first -); sending the full ikey there gets the request rejected with Collector-Error: Invalid Tenant Token.
Validation
Verified end-to-end against the live OneCollector ingest with a real ikey: post-fix, a single Heartbeat envelope returns status: 200, body: {"acc":1}.
Fix
Fixed by #456 (also included: kill-tokens handling, richer DEBUG log on non-2xx, consent prompt rebrand).
Closing as fixed.
Symptom
DEBUG log:
telemetry backend returned 400(also seen as 401 depending on the exact rejection path). All telemetry events have been silently dropped since the OneCollector path shipped — clients don't notice because errors in the telemetry pipeline are intentionally swallowed.Root cause
The exporter was embedding the full instrumentation key in both the
x-apikeyHTTP header AND the envelope'siKeyfield. OneCollector expects the envelopeiKeyino:<tenant_token>form (just the portion before the first-); sending the full ikey there gets the request rejected withCollector-Error: Invalid Tenant Token.Validation
Verified end-to-end against the live OneCollector ingest with a real ikey: post-fix, a single Heartbeat envelope returns
status: 200, body: {"acc":1}.Fix
Fixed by #456 (also included:
kill-tokenshandling, richer DEBUG log on non-2xx, consent prompt rebrand).Closing as fixed.