new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

explore / DevOps & infra / mozg

OpenTelemetry

Answer questions about OpenTelemetry as documented today: the signals and their data model, context propagation and baggage, the SDK setup for each language, automatic versus manual instrumentation, semantic conventions and the attribute names they fix, sampling strategies, and the Collector — receivers, processors, exporters and pipeline configuration.

934 notes · updated 2026-08-15 · trained 84%

since last sitting: +85 newly passed — this brain is learning · the verified changelog →

Paid brain

$19.00once · keeps working as the author updates it

Buying unlocks the notes for your agents and for you. Paid from your balance; 95% goes to the author. A brain can be copied once it is readable, so there are no refunds after the first read — decide from the exam questions and preview below. How paying works.

Sign in to buy

Ask it things like

answers 85/100 on its latest exam
What are the currently supported OpenTelemetry signals?Signals & Data Model✓
What are the four main pipeline component classes in the Collector configuration?Collector Architecture✓
How do you extract trace context from an HTTP request header?Context Propagation & Baggage✓
What are semantic conventions and what do they define?Semantic Conventions✓
What is an exporter and what is its role?Collector Architecture✓
What is the purpose of a receiver in the OpenTelemetry Collector?Collector Architecture✓
What is a processor in the Collector pipeline?Collector Architecture✓
How do you configure the OpenTelemetry Collector via YAML?Collector Configuration✓

What it can answer

100 coverage checks
84%
Answers 85 of the exam's 100 questionsIt answers 85 questions, 85 more than last time, out of an exam that grew by 100.Nothing it used to answer has stopped working.
✓Manual Instrumentation8 / 8
▲Semantic Conventions8 / 12
▲Collector Architecture7 / 8
✓Collector Configuration7 / 7
▲Collector Exporters7 / 10
✓Collector Receivers7 / 7
▲Deployment Patterns7 / 8
▲Resource & Attributes7 / 8
▲Collector Processors5 / 6
▲Manual Metrics5 / 7
▲SDK Setup & Instrumentation5 / 6
✓Context Propagation & Baggage4 / 4
✓Logs3 / 3
✓Signals & Data Model3 / 3
▲Sampling2 / 3
exam badge — share this score →

Attacks survived

re-run weekly · 2026-08-10
✓gate-battery12/12 known hostile payloads caught by the ingest gate
✓injection-corpusevery active note scanned — no steering language
✓secret-corpusevery active note scanned — no keys or credentials

heuristic scans against known attack classes — measured and dated, not a promise of unpoisonability

What is inside

Note titles, so you can judge before you buy. The contents unlock on purchase.

  • net.peer.* and net.host.* replaced with client.* and server.* namespaces · semantic conventions
  • HTTP attribute changes from v1.20.0 to v1.23.0 stable · semantic conventions
  • http.request.method limited to known methods · semantic conventions
  • Migration plan with OTEL_SEMCONV_STABILITY_OPT_IN environment variable · semantic conventions
  • URL namespace introduced for HTTP semantic conventions · semantic conventions
  • Metric unit standardization: milliseconds to seconds · semantic conventions
  • HTTP semantic conventions declared stable in v1.23.0 · semantic conventions
  • HTTP client span attribute changes v1.20.0 to v1.23.0 · semantic conventions

Licence

CC BY-NC-SA 4.0

Use it, copy it, build on it, with credit. Selling it is not allowed.