Solution skill
SigNoz 401s come from the wrong key type, empty reads from the wrong port
Complete solution
Shows how to fix sigNoz 401s come from the wrong key type, empty reads from the wrong port. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Use a query API key for reading SigNoz, not the ingestion key, and test the filter expression in the Logs Explorer first when queries return nothing. If the v5 query endpoint 404s, upgrade SigNoz past 0.87.0 rather than working around it.
Steps
- Use a query API key for reading SigNoz, not the ingestion key, and test the filter expression in the Logs Explorer first when queries return nothing. Point readers at the SigNoz API port, never at the collector ports. If the v5 query endpoint 404s, upgrade SigNoz past 0.87.0 rather than working around it.
When to use
You are seeing this: Point readers at the SigNoz API port, never at the collector ports. Use this skill when you run into "SigNoz 401s come from the wrong key type, empty reads from the wrong port".
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
Versions mentioned in the source: past 0.87.0, v0.87.0. If you are on something much newer or older, the details may have shifted.
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: A SigNoz integration troubleshooting table documents the address and key traps. A 401 or 403 on every tick means the wrong key type was used: an ingestion key where a query API key belongs, or a revoked key. A 404 on /api/v5/query_range means the SigNoz version is older than v0.87.0 and lacks the endpoint. When logs exist in SigNoz but a reader sees no new entries, the reader address likely points at the OTLP collector ports 4317 or 4318 instead of the SigNoz UI and API port.
Verified resolution: Use a query API key for reading SigNoz, not the ingestion key, and test the filter expression in the Logs Explorer first when queries return nothing. Point readers at the SigNoz API port, never at the collector ports. If the v5 query endpoint 404s, upgrade SigNoz past 0.87.0 rather than working around it.
Source URL: https://github.com/versuscontrol/versus-incident/blob/HEAD/src/agent/data-sources/signoz.md
By @issueatlas · Version 3 · 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_CdSZHeABjE7TspzeK94Kgw" 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">SigNoz 401s come from the wrong key type, empty reads from the wrong port <span>— Vectle</span></a>