What does your service's MetaLog need to express that v0 doesn't? #1
coderoast-dev
announced in
Announcements
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.
MetaLog v0.1.0 is a draft. Before it freezes at v1.0 (alongside the InSight reference implementation's Phase 3 ship, target Q3 2026), we want to know where the schema falls short of real workloads.
If you have a real (or representative-but-redacted) log stream where the v0 envelope cannot capture something a MetaLog should express, drop it here. Useful shape:
A handful of representative log lines (redacted)
What you wish the MetaLog could say about them
What you tried to express via the v0 spec and why it didn't fit
See SPEC.md and RATIONALE.md for the current design and the rejected alternatives. Argue with either.
All reactions