docs(rfc-0002): add §10 open question on first-class OTel query dimensions - #26
Merged
Merged
Conversation
…sions External feedback (OpenTelemetry maintainer guidance, May 2026) notes that `service.name`, `trace_id`/`span_id`, `scope_name`, and typed `attributes` are the primary dimensions a log backend is judged on for cross-signal correlation. RFC 0001 §6.1 already stores them as faithful columns, but the storage spec doesn't prescribe how the DSL surfaces them. Adds a §10 open question so the DSL design decides this — named ergonomic accessors (e.g. `service ==`, `trace_id ==`, `attr["k"] ==`) rather than hand-written attribute-map lookups — before §9 user research, and so RFC 0001 doesn't have to retrofit it later. No design change in this PR; just a tracked open question. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Captures external OTel-community feedback (OpenTelemetry maintainer guidance, May 2026) as a tracked §10 open question on RFC 0002.
The feedback:
service.name(viaresource_attributes),trace_id/span_id,scope_name, and typedattributesare the primary correlation/query dimensions a log backend is judged on. RFC 0001 §6.1 already stores them as faithful columns (this is what the PR #21/#23/#24 wave landed); the gap is that the storage spec doesn't prescribe how the DSL surfaces them.The new open question asks RFC 0002 to commit to ergonomic, named accessors (e.g.
service ==,trace_id ==,attr["k"] ==) rather than requiring users to hand-write attribute-map lookups — and to settle the surface here so RFC 0001 doesn't need to retrofit it.Changes
No design change; nothing else touched.
Test plan
mdbook buildclean locally🤖 Generated with Claude Code