observability-fundamentals

Name: observability-fundamentals
Availability: InStock
Author: Honeycomb

Explain observability principles, wide events, and high cardinality.

20|7|Updated Feb 7, 2026

Search Tags:#debugging #monitoring #metrics #fundamentals #observability #telemetry #events

Ready to run

npx skills add https://github.com/honeycombio/agent-skill --skill observability-fundamentals

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability-fundamentals
Source: https://github.com/honeycombio/agent-skill/tree/main/honeycomb/skills/observability-fundamentals
Command: npx skills add https://github.com/honeycombio/agent-skill --skill observability-fundamentals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill clarifies the fundamental concepts of observability, helping users understand why Honeycomb's approach is effective and how it differs from traditional monitoring.

Core Features & Use Cases

Explain Core Concepts: Defines and differentiates observability, wide events, high cardinality, and the core analysis loop.
Contextualize Data: Explains the value of wide events over metrics and logs for debugging.
Use Case: A new engineer asks, "What exactly is observability and why should we use Honeycomb?" This skill provides a clear, foundational answer.

Quick Start

Explain the first principles behind observability.

Frequently Asked Questions about observability-fundamentals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is observability and how does it differ from traditional monitoring?▼

Observability is the ability to understand internal system states from external outputs. It differs from traditional monitoring by utilizing high cardinality data and wide events to enable open-ended investigation, rather than relying on predefined metrics and logs.

Why use wide events instead of metrics and logs for debugging?▼

Wide events provide rich, structured telemetry that preserves context for complex debugging. Unlike isolated metrics or logs, wide events capture every attribute of a request, enabling high cardinality analysis to pinpoint anomalies and investigate unknowns.

What is high cardinality data in observability and why is it important?▼

High cardinality data in observability refers to telemetry fields with many unique values, like user IDs or request traces. It is important because it allows you to slice and group system events dynamically to isolate specific issues during investigation.

How does the core analysis loop work in observability?▼

The core analysis loop in observability works by iteratively querying wide events to form hypotheses about system behavior. You slice telemetry by various attributes, observe the results, and refine your queries until you pinpoint the root cause of an issue.

When do I need observability for my software engineering workflow?▼

You need observability when debugging complex, distributed systems where traditional monitoring falls short. It is essential when you must trace unpredictable failures, analyze high cardinality data, or ask new questions about your system without deploying new instrumentation.