observability-standards

Configure Laravel logging with correlation IDs and structured log formats.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill observability-standards-majedsiefalnasr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-standards
Source: https://github.com/majedsiefalnasr/bunyan-app-cursor/tree/main/.agents/skills/observability-standards
Command: npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill observability-standards-majedsiefalnasr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consistent observability is hard when logs are fragmented, making debugging and incident response slower. This skill sets clear guidelines for structured logging, correlation IDs, and monitoring to improve visibility across services.

Core Features & Use Cases

  • Structured logging: enforce uniform log formats and contextual data in Laravel controllers and services.
  • Correlation IDs: propagate and log a unique request ID across middleware and endpoints to trace requests end-to-end.
  • Monitoring readiness: establish log channels, basic audit logs, and a minimal monitoring checklist for quick validation in CI/CD.

Quick Start

Configure Laravel to use structured logs and a correlation ID middleware, and begin emitting contextual log messages in API controllers.

Frequently Asked Questions about observability-standards

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

FAQPage Schema
How do I implement structured logging with correlation IDs in Laravel?

Structured logging in Laravel is enforced by configuring dedicated log channels and implementing middleware to propagate correlation IDs. This ensures uniform log formats and consistent contextual data across controllers and services.

What is a correlation ID and how does it improve API observability?

A correlation ID is a unique request identifier propagated across Laravel middleware to trace requests end-to-end. It improves API observability by linking fragmented logs, which accelerates debugging and incident response across backend services.

How do I configure Laravel log channels for better request monitoring?

Configuring Laravel log channels for request monitoring involves establishing structured formats and audit logs. This creates monitoring readiness and provides a minimal checklist for quick validation in CI/CD pipelines.

Can I use this structured logging approach for Laravel API endpoints specifically?

Yes, this structured logging approach specifically targets Laravel-based backend services and API endpoints. It prescribes emitting contextual log messages in API controllers to capture request details and error context uniformly.

Why are my Laravel application logs fragmented and hard to debug?

Laravel application logs become fragmented when they lack structured formats and correlation IDs. Implementing request-logging middleware with consistent contextual data resolves this by linking logs end-to-end for faster incident response.