← all corpora

otel-proto

reference corpus · status live · domain OPS (Operations and SRE) · lane A · refresh pinned · tags GLOBAL · OPERATIONS

What an agent uses it for

an agent wiring telemetry queries this for the exact semantic conventions and proto field semantics

Use it
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/otel-proto.json
xerj corpus add --from ./otel-proto.json
xerj corpus index otel-proto then xerj code otel-proto "your question"

Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "otel-proto", once the corpus is indexed on the node.

Sources and pins

sourcepinlicencesizereview note
opentelemetry-proto b3f75588eb23Apache-2.0 0 B / 0 files OpenTelemetry protocol definitions (.proto) at the pinned commit. Primary content rides the plain-text family: every .proto file is a txt-lines record, so the corpus declares query.text_weight 1.0 (#1254): at the default 0.5 the definitions rank 19-39 behind semantic-conventions prose on the same index bytes.
corpus-otel-semconv-docs 15f75ec34e95Apache-2.0 (mirror LICENSE) / CC-BY-4.0 (mirrored docs) 4.7 MB / 297 files semantic-conventions docs mirror (markdown, heading-sectioned), companion prose beside the definitions. The mirror repo's own LICENSE file is Apache-2.0, but the mirrored upstream files are open-telemetry/semantic-conventions docs, which are CC-BY-4.0: attribution to upstream is required when adapting their text; the stricter of the two governs.

4.7 MB across 297 files. Added 2026-10-04.

People behind this corpus

Upstream authors (2)

Owners of the pinned repositories, credited under each repository's licence. They have not signed up here; their pages are attribution.

open-telemetry@open-telemetry · upstream
xerj-org@xerj-org · upstream

All contributors.

Rights

Apache-2.0 + Apache-2.0 (mirror LICENSE) / CC-BY-4.0 (mirrored docs). Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.

Retrieval spot-check (G7)

0.0/5 relevant. Graded .

Q: Which OTLP span kind should I use for a component that publishes a message to a queue?
expect:
top-5: otel-proto-2/docs/messaging/messaging-spans.md / otel-proto-1/docs/specification.md / otel-proto-2/docs/general/trace.md / otel-proto-2/docs/messaging/messaging-spans.md / otel-proto-2/docs/messaging/gcp-pubsub.md
grade: miss
Q: Why does OTLP wrap attribute arrays in a separate ArrayValue message instead of a repeated field in AnyValue?
expect:
top-5: otel-proto-1/docs/specification.md / otel-proto-1/docs/specification.md / otel-proto-1/docs/specification.md / otel-proto-1/CONTRIBUTING.md / otel-proto-1/CHANGELOG.md
grade: miss
Q: How should HTTP spans be named according to the OpenTelemetry semantic conventions?
expect:
top-5: otel-proto-2/CHANGELOG.md / otel-proto-2/docs/rpc/grpc.md / otel-proto-2/CHANGELOG.md / otel-proto-2/docs/general/trace.md / otel-proto-2/docs/non-normative/code-generation.md
grade: miss
Q: Should the raw database query text be recorded on spans by default?
expect:
top-5: otel-proto-2/docs/db/cassandra.md / otel-proto-2/docs/db/elasticsearch.md / otel-proto-2/docs/db/oracledb.md / otel-proto-2/docs/db/sql-server.md / otel-proto-2/docs/db/postgresql.md
grade: miss
Q: In OTLP, how do I tell a Sum metric that only ever goes up from one that can also go down?
expect:
top-5: otel-proto-2/docs/non-normative/groups/system/design-philosophy.md / otel-proto-2/docs/non-normative/groups/system/design-philosophy.md / otel-proto-2/internal/tools/tools.go / otel-proto-2/docs/non-normative/groups/system/cpu-metrics-guidelines.md / otel-proto-2/docs/general/naming.md
grade: miss

Agent score

From structured reviews that AI agents send after they use this corpus: through xerj hub pull, MCP queries, or the xerj_corpus_feedback tool. Each review rates usefulness 1–5, whether the answer was found, and freshness. This is not the human hub star count shown above. The two are never mixed.

Loading agent reviews…

Score = Bayesian mean of usefulness (prior 3.0 with weight 5), so a few reviews cannot swing it. One voice per installation per corpus per week; abnormal-volume reviewers are dropped. Coverage gaps appear only once 3 or more agents report the same one. How it works.

Traffic

Traffic stats load from /api/hub-traffic when this page runs JavaScript.

Views: visits to this page (search-engine crawlers excluded). Unique: distinct visitors per day, by a hash salted with the day, so the 14-day unique figure adds up daily uniques. Pulls: growth of the GitHub release download count of this corpus’s pack (xerj hub pull downloads from there; includes our own pack-verification downloads). Searches: hosted-hub queries for this corpus. Referring sites appear after 3 views. What is collected.

Agent usage

Usage stats load from /api/hub-usage when this page runs JavaScript.

Counted: requests agents send to the hosted hub API (hub.xerj.org/api/v1/code, /def) for this corpus. Queries on your own node (xerj code, xerj ask with a local pack, the MCP tools) never leave your machine and are not counted. Templates replace identifiers, versions, paths, numbers and quoted text with placeholders; one is shown only once it has been seen 3 times in 30 days, and any word asked fewer than 3 times shows as <term>. Raw queries are never published. What is collected.