telemetry
The data a running system sends out about itself, such as logs, metrics and traces.
In more detail
Telemetry is evidence emitted by software while it runs, collected so that people and tools can understand its behaviour. The three main kinds are logs, metrics and traces.
Examples
In the browser: Telemetry should never slow the page it measures: schedule it in idle time and send it with fetch keepalive or sendBeacon so it survives page unload.The course service emits all three kinds for every request.React error boundaries typically report caught errors and their component stack to a monitoring service from componentDidCatch.Related terms
- OpenTelemetry — A vendor-neutral, open-source standard and set of tools for producing traces, metrics and logs and sending them to any backend.
- metric — A number measured over time, such as requests per second or error count, that shows how a system behaves in aggregate.
- log — A time-stamped record of an individual event in a system, such as one request being handled; structured logs record it as named fields rather than free text.
- trace — A record of one request’s whole journey through a system, made of nested spans that show where the time went.
- observability — How well you can understand what a system is doing, and why, from the data it emits: mainly logs, metrics and traces.
- personally identifiable information — Any information that can identify a person, directly or combined with other data, such as a name, email address, location or account number.
- requestIdleCallback — A function that schedules low-priority work to run when the browser has spare time at the end of a frame.
- fetch keepalive — A fetch option, keepalive: true, that lets a small request keep going after the page that started it has been closed or navigated away.
- real-user monitoring — Measuring performance from real visitors' browsers and sending the data back, instead of only testing in a lab.
- structured logging — Writing each log entry as named fields, such as status, duration and request identifier, instead of a free-text sentence.
- redaction — Removing or hiding sensitive values, such as tokens or personal data, before data is logged, displayed or shared.
- analytics — Collecting data about how visitors use a site, such as page views and clicks.
- span — One timed operation within a trace, such as handling a request or running a query, with its start, duration and attributes.
- telemetry signal — One of the three main kinds of telemetry: metrics, logs or traces.
- instrumentation — Code, often a library, that makes an application emit telemetry about its operations.
- componentDidCatch — A class lifecycle method React calls after a child error, receiving the error and an info object whose componentStack shows which components were rendering.
- error boundary — A class component that catches errors thrown while rendering its children and shows a fallback UI instead of crashing the whole app.
Taught in
- Admin Processes And The Open Source Update — DevOps & Site Reliability Engineering
- Service Level Indicators — DevOps & Site Reliability Engineering
- Service Level Objectives — DevOps & Site Reliability Engineering
- Internal Developer Platforms — DevOps & Site Reliability Engineering
- Observability Context — DevOps & Site Reliability Engineering
- Retry and Circuit Breaker Policies with Polly — Modern .NET Core, C# & Enterprise Microservices
- OpenTelemetry, Container Publishing and Trimming — Modern .NET Core, C# & Enterprise Microservices
- requestAnimationFrame vs requestIdleCallback: High-FPS Work — Frontend Architecture & Web Platform
- The Fetch API: Streaming Responses, HTTP Caching And Keepalive — Frontend Architecture & Web Platform
- Core Web Vitals: Measuring And Optimizing LCP, INP, And CLS — Frontend Architecture & Web Platform
- Environment Configuration: Secrets & Multi-Stage — Production Full-Stack Engineering
- Distributed Tracing: OpenTelemetry & Traceparent — Production Full-Stack Engineering
- Structured Logging & Correlation IDs: Context Stitching — Production Full-Stack Engineering
- Continuous Delivery: Blue-Green & Canary Pipelines — Production Full-Stack Engineering
- Server Components: Async Execution & Constraints — Next.js 15 & Modern App Router Architecture
- Templates vs Layouts: Remounting & Page Transitions — Next.js 15 & Modern App Router Architecture
- Instrumentation: OpenTelemetry & Performance Spans — Next.js 15 & Modern App Router Architecture
- Containerized Deployment: Multi-Stage Docker Builds — Next.js 15 & Modern App Router Architecture
- Timers Phase: setTimeout, Min-Heap Scheduling & Drift — Node.js Internals & Backend Services
- Close Phase & Signal Dispatch: Sockets & Teardown — Node.js Internals & Backend Services
- Global Error Trapping: uncaughtException & Exits — Node.js Internals & Backend Services
- Observability Versus Monitoring — Full-Stack Observability: Metrics, Tracing & Logging
- The Three Signals: Logs, Metrics And Traces — Full-Stack Observability: Metrics, Tracing & Logging
- OpenTelemetry: The Vendor Neutral Path — Full-Stack Observability: Metrics, Tracing & Logging
- The OpenTelemetry Collector — Full-Stack Observability: Metrics, Tracing & Logging
- Instrumenting A Service With Client Libraries — Full-Stack Observability: Metrics, Tracing & Logging
- Fifteen Traces For Six Bookings: Where Context Was Lost — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Ninety Minutes, No Question Count: Exam Strategy — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Two Names For One Fact: Semantic Conventions And Resources — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Traces From A Script Nobody Touched: Instrumentation Approaches — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fundamentals Sprint: One Declined Card — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fifty Two Spans, Four Requests: The Trace Data Model — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Validated And Deaf: Checking A Collector Config — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fifty Five In, Fifty Two Out: Transforming Data — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Collector Sprint: Sixteen Predictions — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Fifty Four In, Two Out: Debugging A Pipeline — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Failed Twice, Flushed Fine: Error Handling And Schemas — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Maintenance Sprint: Symptoms First — OpenTelemetry Certified Associate (OTCA) Exam Prep
- The Evening Before: Final Review — OpenTelemetry Certified Associate (OTCA) Exam Prep
- Error Boundaries: componentDidCatch And Fallback UI Trees — React 19 & Modern Component Architecture
References
- OpenTelemetry: what is OpenTelemetry
- OpenTelemetry: signals
- MDN: Navigator.sendBeacon()
- OpenTelemetry: Observability primer