Results for “logging”

53 skills

claude-dev-suite

Java logging with SLF4J facade, Logback, and Log4j2 implementations. Covers configuration, log levels, structured logging, async logging, and production best practices for Spring Boot applications. USE WHEN: user mentions "java logging", "spring boot logging", "slf4j setup", asks about "how to log in java", "logback vs log4j2", "java logging best practices" DO NOT USE FOR: Node.js logging - use `nodejs-logging` instead, Python logging - use `python-logging`, Kotlin-specific logging - similar but has nuances

claude-dev-suite

Node.js logging with Winston, Pino, and built-in console. Covers structured logging, log levels, transports, async logging, and production best practices for Express/NestJS applications. USE WHEN: user mentions "node.js logging", "express logging", "nestjs logging", asks about "how to log in node", "winston vs pino", "node logging best practices" DO NOT USE FOR: Python logging - use `python-logging` instead, Java logging - use `slf4j` or `logback`, Browser logging - different environment and APIs

claude-dev-suite

Python logging with the standard library logging module and structlog. Covers log levels, handlers, formatters, structured logging, and production best practices for FastAPI/Django applications. USE WHEN: user mentions "python logging", "fastapi logging", "django logging", asks about "how to log in python", "python logging module", "logging configuration python" DO NOT USE FOR: Node.js logging - use `nodejs-logging` instead, Java logging - use `slf4j` or `logback`, structlog-specific - use `structlog` skill for deep dive

claude-dev-suite

Pino - extremely fast and low overhead Node.js logger with JSON-native structured logging. 10x faster than Winston. Optimized for high-performance APIs and production environments. USE WHEN: user mentions "pino", "fast logging", "high performance logging", "fastify logging", asks about "fastest node.js logger", "JSON structured logging", "low overhead logging" DO NOT USE FOR: Winston logging - use `winston` instead, Python logging - use `python-logging` instead, Complex transport requirements - use `winston` instead

hoangnguyen0403

Standards for structured logging and observability in Golang. Use when adding structured logging or tracing to Go services.

More results

observability-and-instrumentation

Adds logging, metrics, tracing, and alerting to make production behavior visible and diagnosable.

Log in Node.js with Pino. Use when a user asks to add structured logging, improve logging performance, configure log levels, format logs for production, or replace console.log with proper logging.

debug-and-logging

Diagnose Apex behavior with debug logs, structured production logging, and async job monitoring, replacing ad-hoc System.debug habits with durable, queryable observability.

log-hauling-operations

Use this skill when the user asks about logging / log hauling operations — short-haul exemption specifics for logging, log truck securement, axle weights, state-by-state logging permits (especially OR, WA, ID, BC), bunk + stake configurations, and how logging fits into FMCSA + state rules. Reference 49 CFR 393 for cargo securement of logs.

projectious-work

logging-strategy

Structured logging strategy — levels, correlation IDs, context propagation, PII avoidance. Use when designing a logging approach, reviewing log statements, setting up log aggregation (ELK, Loki, CloudWatch), adding correlation IDs to a distributed system, or deciding what to log and what to keep out.

init-next-logging

Initializes production-ready logging for a Next.js project using Pino and pino-roll, with file output, log rotation, and request context. Handles server-side and client-side environments, including Vercel/serverless setups.

Design, review, and troubleshoot Salesforce Flow fault handling with error logging and bulk-safe automation paths.

configuring-opentelemetry-dotnet

Configure OpenTelemetry distributed tracing, metrics, and logging in ASP.NET Core using the .NET OpenTelemetry SDK.

Guides building secure admin panels with RBAC, audit logging, and step-up controls for privileged actions.

monitoring-expert

Configures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, and instruments distributed tracing.

10.4k · bundle

dataverse-python-production-code

Generate production-ready Python code using the Dataverse SDK with error handling, retry logic, OData optimization, and logging.

orchestra-research

experiment-tracking-swanlab

Track ML experiments with open-source run logging, local or self-hosted dashboards, and media visualization using SwanLab.

10.4k · bundle

springboot-patterns

Provides Spring Boot architecture patterns for building scalable REST APIs, including layered services, data access, caching, async processing, and logging.

Log workouts, plan routines, track progress, and get intelligent coaching for any fitness level.

Loki is a horizontally scalable log aggregation system built by Grafana Labs. Unlike traditional log platforms that index the full text of every log line, Loki indexes only metadata labels, making it significantly cheaper to operate. It integrates natively with Grafana for querying and visualization, and uses LogQL — a query language inspired by PromQL — to filter, parse, and aggregate log streams.

Log and search local text entries from the command line. Use when adding quick notes, searching past entries, or exporting a simple activity log.

Essential Zephyr RTOS kernel services. Covers thread lifecycle and priority, the logging subsystem for diagnostics, and the interactive shell for real-time hardware inspection and debugging. Trigger when writing application flows, adding logging to modules, or creating interactive CLI commands.

projectious-work

standup-context

Writes a structured standup update as a session.standup LogEntry — capturing what was done, what is in progress, what comes next, and any blockers. Use when the user says "write a standup", "standup update", "what did I do today", "write a status update for the team", or at the end of a session on projects that run daily standups.

projectious-work

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

jrennie99-glitch

Search and analyze your own session logs (older/parent conversations) using jq.

Diagnose your own behavior by reading the structured logs you leave behind — turns.jsonl, events.jsonl, chat_history.jsonl, scheduler.yaml. Use when something has gone wrong (a message didn't land, a scheduled job isn't firing, a communication pattern feels off), when you need to understand a pattern over many turns, or when cost / token usage needs auditing. Covers jq query recipes and points at the debugging-jobs / debugging-communication / debugging-drift companion guides for specific failure modes.

Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix.

Debug application issues with techniques for Python, JavaScript, performance profiling, production incidents, and network problems.

Monitor SLURM/PBS jobs and their logs. Use when the user asks to monitor, check, or watch a submitted job. Automatically detects running/pending jobs, tails logs, and reports errors.

Track food and nutrition. Use when logging meals, checking calories, tracking protein/carbs/fat, or generating diet reports.

Reads and analyzes application logs for debugging and monitoring.

aniruddhaadak80

Search and analyze your own session logs (older/parent conversations) using jq.

Search and analyze your own session logs (older/parent conversations) using jq.

debugging-methodology

Debugging is the scientific method under time pressure.

Use when implementing loki functionality with production-grade patterns and safeguards.