mohsen_hassani/LedgerLine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct OTLP metrics/logs behaviour to 404, and start Phase 2

Browse Source 
Alloy only registers an OTLP/HTTP route for a signal with an output, so
POST /v1/metrics and /v1/logs return 404 rather than being accepted and
silently dropped (verified live against otlp.vione.cloud). Fix the claim
everywhere it appeared. Also mark Phase 2 in progress.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Movses Aslanyan
2026-10-12 20:09:38 +03:30
co-authored by Claude Opus 5.5
parent 7719ef5fcf
commit 995c93982a
8 changed files with 29 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
k8s/README.md
+2 -1
View File
@@ -43,7 +43,8 @@ OTLP/gRPC (4317) is cluster-internal only. Apps use OTLP/HTTP.
empty in the role too; see `prometheus/prometheus.yml`).
The CLAUDE.md platform facts still hold:
- OTLP metrics and logs are silently dropped.
- OTLP metrics and logs are rejected: Alloy returns a 404 on `/v1/metrics` and
`/v1/logs`, so the only sign is an export error in the app's own logs.
- Span metrics and the service graph come from Tempo's metrics-generator.
- The Loki derived field matches lowercase `trace_id`.
- Datasources are provisioned; dashboards are not.