logbox

Configure LogBox appenders, categories, and async logging for ColdBox applications.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ColdBox/skills --skill logbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logbox
Source: https://github.com/ColdBox/skills/tree/main/logbox
Command: npx skills add https://github.com/ColdBox/skills --skill logbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and standardizes logging configuration for ColdBox and standalone LogBox so teams avoid inconsistent logging, noisy outputs, and expensive log evaluations that slow applications or overwhelm operators.

Core Features & Use Cases

  • Appender configuration and selection including console, file, rolling, DB, scope, socket, and email for development and production routing.
  • Category-based inheritance, root logger control, and WireBox injection to provide per-package logging policies without code changes.
  • Performance and observability patterns: closure messages, can{} guards, structured extraInfo handling, async appenders, and guidance for rolling files and retention.
  • Extensibility for custom appenders and layouts to forward logs to webhooks, ELK, or cloud providers while applying production best practices like redaction and async tradeoffs.

Quick Start

Configure LogBox to use a console appender for development and a rolling file appender for production, set package-level categories for INFO and enable async on high-volume appenders.

Frequently Asked Questions about logbox

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

FAQPage Schema
How do I configure structured logging in ColdBox for production?

Configure structured logging in ColdBox by setting up LogBox with a console appender for development and a rolling file appender for production, defining package-level categories for INFO severity, and enabling async behavior on high-volume appenders.

Can I prevent expensive logging evaluations in ColdBox without removing log statements?

Yes, you can prevent expensive logging evaluations by using closure messages and can{} performance guards. These mechanisms defer message construction until the logger confirms the target appender will actually process the specified log level window.

What's the best way to route ColdBox logs to external systems like ELK or webhooks?

The best way to route logs to ELK or webhooks is by building custom appenders and layouts. This extensibility pattern allows you to forward structured log data to cloud providers while applying production best practices like data redaction.

How does category-based inheritance work for ColdBox logging policies?

Category-based inheritance allows you to define per-package logging policies through root logger control and WireBox injection. This enables granular severity and appender routing for specific code packages without requiring changes to existing application code.

Does LogBox support asynchronous logging for high-volume production environments?

LogBox supports asynchronous logging by enabling async behavior on high-volume appenders. This production pattern prevents logging operations from blocking application threads, while rolling file retention policies manage long-term disk usage.

How do I handle structured extra information in ColdBox log entries?

Handle structured extra information in ColdBox log entries through structured extraInfo handling. This feature allows you to pass complex data alongside log messages, which custom appenders can then format and route to destinations like databases or sockets.