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
docs/roadmap/phase-2.md
+4 -3
View File
@@ -2,10 +2,11 @@
*Part of `docs/roadmap/` — see [`intro.md`](intro.md) for platform/background context and [`summary.md`](summary.md) for how every phase fits together. Prev: [`phase-1.md`](phase-1.md) · Next: [`phase-3.md`](phase-3.md)*
**Status:** Not started
**Status:** In progress
**Message:** Blocked on nothing — Phases 0 and 1 are done and the platform is
described above. Waiting to begin.
**Message:** Started 2026-10-12. Step 1 (deploy the platform) is done and
verified live, apart from reading the Alloy component graph. Next: step 2,
zero-code auto-instrumentation of `sanctions`.
**Time-box:** one evening.