observability

Configure LogTape and JSONL logging with correlation IDs for Bun applications.

2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/nathanvale/side-quest-marketplace --skill observability-nathanvale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/nathanvale/side-quest-marketplace/tree/main/plugins/dev-toolkit/skills/observability
Command: npx skills add https://github.com/nathanvale/side-quest-marketplace --skill observability-nathanvale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establish robust observability across Bun-based tooling, with structured JSONL logs, correlation IDs, and hierarchical categories.

Core Features & Use Cases

  • LogTape & JSONL: Structured, machine-parsable logs for analysis.
  • Correlation IDs: Trace requests across subsystems.
  • Hierarchical categories: Filter logs by plugin/subsystem.
  • Performance metrics: Timed operations and dashboards for observability.

Quick Start

Initialize the plugin logger, create a correlation ID per operation, and log across subsystems.

Frequently Asked Questions about observability

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

FAQPage Schema
How do I set up structured logging for a Bun application?

Structured logging for Bun apps uses LogTape with JSONL output format. Initialize a plugin logger, configure hierarchical categories for your subsystems, set log levels, and logs automatically include timestamps. This produces machine-parsable records suitable for grep-based analysis and log rotation.

What are correlation IDs and how do I use them across subsystems?

Correlation IDs are unique identifiers that trace a single request or operation across multiple plugin subsystems. Generate one per operation and include it in logs to link related events together, enabling you to follow execution flow and debug interactions between components.

Can I filter logs by plugin or subsystem?

Yes, hierarchical categories let you organize logs by plugin or subsystem. Configure per-subsystem loggers with category names, then filter JSONL output during analysis to isolate logs from specific components for targeted debugging.

Does this Skill support performance metrics collection?

Yes, the Skill collects performance metrics including timed operations. This enables you to measure subsystem performance and feed data into dashboards or observability platforms for production monitoring.

How do I analyze JSONL logs after they're generated?

JSONL output is line-delimited JSON, making it grep-friendly and parseable by standard Unix tools and log aggregators. Each log entry is a complete JSON object containing timestamp, correlation ID, category, and message for easy filtering and analysis.