agentleFS
ollygardenollygarden/opentelemetry-agent-skills/skills/otel-telemetry-emissions/SKILL.md

otel-telemetry-emissions

Skill126 starsChanged 4 months agoApache-2.0View on GitHub

Version-pinned inventory of the telemetry (spans, metrics, logs, attributes) emitted by OpenTelemetry collector components and SDK instrumentation packages. Use when working with a covered component — what it emits at a given version, or how emission changed across versions — and when upgrading a component or SDK version, to see the telemetry after the change.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If there is no exact match, use the file with the highest version below the target and say the exact version is unverified.

    line 31
  2. Distinctive:

    If the component or version is not covered at all, say so — do not infer telemetry from semantic conventions.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Telemetry Emissions

A registry of what telemetry OpenTelemetry components actually emit, pinned to upstream versions.

Note: The telemetry emissions in these files were detected by LLM analysis of the upstream source and may contain errors. Verify against the component's source or docs before relying on a row for critical decisions.

Layout

<repo basename>/<path in repo>/v<version>.md

Example: opentelemetry-collector-contrib/receiver/kafkareceiver/v0.158.0.md

One file per scanned version. The files in a component directory are its telemetry history; index.md lists every file — start there to see what is covered.

Looking up a component at a version

  1. Find the component's directory (or its row in index.md).
  2. Pick the file matching the target version exactly.
  3. If there is no exact match, use the file with the highest version below the target and say the exact version is unverified.
  4. If the component or version is not covered at all, say so — do not infer telemetry from semantic conventions.

What a data file contains

Frontmatter (repo, path, version, scope_name, commit_sha, last_verified), then per-signal tables:

  • Traces — span name, kind, attributes, notes
  • Metrics — metric name, instrument type, unit, attributes, notes
  • Logs — log/event name, attributes, notes

scope_name is the component's instrumentation scope — the anchor for matching runtime telemetry back to the component. When helper or pipeline telemetry uses another scope, its rows name that scope in Notes. last_verified: null means the historical verification date could not be substantiated; recheck the pinned source before presenting its rows as verified. Absent signals are omitted entirely. Notes marks conditional emission (feature gates, opt-in config, experimental semconv). Sources lists the upstream files the data came from.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.