Repository navigation
A small diagnostic CLI to verify self-hosted Kubernetes OTLP ingestion #11786
ahmedb24
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey SigNoz team & community,
I've noticed that debugging self-hosted Kubernetes ingestion can be tricky. Sometimes it's a missing endpoint, a broken service selector, or a blocked OTLP port (4317/4318) making it hard to tell if SigNoz is broken or if it's just cluster networking.
I built signoz-otlp-verify to automate these checks. It runs locally (via port-forwarding) or as an in-cluster Job, sends a synthetic trace explicitly tagged with is_synthetic=true for easy cleanup and queries the /api/v5/query_range endpoint to prove the data actually arrived.
Features:
• Validates K8s Service Endpoints & Pod Readiness.
• Verifies OTLP/HTTP (4318) and gRPC (4317) reachability.
• Generates a support-ready Markdown/JSON report with actionable remediation hints.
Repo: https://github.com/ahmedb24/signoz-otlp-verify
(There's a quick 30-second demo in the README)
I'd love any feedback from the core maintainers on whether this aligns with the ingestion misconfigurations you see most often!
All reactions