axiom
Implements structured logging and observability with Axiom for serverless applications. Use when adding logging, tracing, and Web Vitals monitoring to Next.js and Vercel applications.
Discover tools monitoring skills, compare source repositories and read the instructions for each workflow.
Implements structured logging and observability with Axiom for serverless applications. Use when adding logging, tracing, and Web Vitals monitoring to Next.js and Vercel applications.
Guide for implementing structured logging in SideQuest plugins using @sidequest/core. Use when adding logging to new plugins, debugging existing plugins, or setting up log analysis.
Best practices for structured logging, correlation IDs, performance metrics, and debugging in Bun applications using @sidequest/core/logging and LogTape. Use when implementing logging, setting up observability,...
Use when troubleshooting host service connectivity, debugging data loading issues, investigating progress tracking problems, diagnosing environment or configuration issues, or checking Grafana dashboards.
Use when diagnosing operation failures, stuck or slow operations, querying Jaeger traces, working with Grafana dashboards, debugging distributed system issues, or investigating worker selection and service comm...
Structured debugging workflow with log server capture and analysis
Grafana dashboard and alert management
Datadog monitoring and observability with native dogshell CLI integration
Queries Sentry for issues, events, traces, and error analysis. Use when debugging production errors, searching issues, analyzing traces, or getting AI root cause analysis with Seer.
Display routine measurement dashboard with metrics, costs, trends, and visualization
Implement application metrics (RED, USE), alerting strategies, and monitoring dashboards
Implement structured logging with appropriate levels, context, and correlation for effective debugging and monitoring
Apply structured logging best practices using Pino for Node.js applications: JSON output, log levels, context, redaction, correlation IDs, and centralization. Use when implementing logging, reviewing log statem...
Mandatory incident fix verification with observables. Invoke after: applying production fixes, before declaring incidents resolved, when someone says 'I think that fixed it'. Requires log entries, metric change...
Logging, debugging, profiling, and performance monitoring for development. Use when adding logging, debugging issues, profiling performance, or instrumenting code for observability.
Use when implementing Go error handling with error wrapping, sentinel errors, and custom error types. Use when handling errors in Go applications.
Create a new configuration profile
Create a new configuration profile
Query Prometheus and Loki billing metrics from Grafana. Use when discussing observability costs, active series, ingestion rates, storage usage, or cardinality analysis.
Production monitoring, observability, SLO/SLI management, and incident response. Trigger terms: monitoring, observability, SRE, site reliability, alerting, incident response, SLO, SLI, error budget, Prometheus...
Sentry error monitoring and user behavior tracking via CLI. Use when: (1) debugging user-reported issues, (2) checking recent errors/crashes, (3) tracing user actions before an error occurred, (4) searching iss...
Configure OpenTelemetry tracing, metrics, and structured logging for DAPR applications. Integrates with Azure Monitor, Jaeger, Prometheus, and other observability backends.
Automatically validate DAPR configuration files (dapr.yaml, component YAML files) when they are created or modified. Checks for schema compliance, missing required fields, invalid values, and common misconfigur...
Proactively detect and diagnose DAPR runtime issues based on error patterns, log analysis, and common misconfigurations. Provides immediate solutions for service invocation failures, state management issues, pu...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.