Implement structured logging, metrics, and tracing with correlation IDs.
npx skills add https://github.com/SylphxAI/flow --skill observability-sylphxai
Please help me install this Agent Skill. Skill: observability Source: https://github.com/SylphxAI/flow/tree/main/.claude/skills/observability Command: npx skills add https://github.com/SylphxAI/flow --skill observability-sylphxai
Observability helps teams understand production behavior and respond quickly to incidents by consolidating logs, metrics, and traces into a cohesive view.
Configure your observability stack by enabling logging, metrics, and tracing in your app, setting up Sentry and PostHog, and deploying to your platform. Then verify end-to-end tracing and alerting in your dashboards.
High-intent search queries and answers about installing and using this skill.
Implement comprehensive observability by enabling structured logging, metrics collection, and tracing in your app, then configure correlation IDs to track requests end-to-end across services. Set up centralized platforms like Sentry for error tracking and PostHog for real-time analytics to consolidate all signals into a cohesive view.
Use end-to-end correlation IDs to trace requests through your entire system. Propagate these IDs across service boundaries so logs, metrics, and traces from each service link together, enabling you to reconstruct the full request path during incident investigation.
Configure alerting on critical failures and establish incident-response workflows that detect issues automatically. By correlating logs, metrics, and traces, you can identify root causes quickly and respond before users are significantly impacted.
Yes. This guidance includes platform-specific recommendations for environments like Vercel, covering how to configure logging, metrics, and tracing within platform constraints and integrate with Sentry and PostHog.
You can use specialized tools like Sentry for centralized error logging and PostHog for real-time analytics and dashboards. Integrating these with your application's native tracing ensures all three signals work together to provide complete observability.
Observability enforces configuration, instrumentation, and incident-response readiness upfront. When production issues occur, you already have structured logs, metrics, and traces in place, enabling fast diagnosis and response instead of scrambling to gather data.
cedriczielInstrument Go applications with OpenTelemetry for traces, metrics, and OTLP export.
FrogAiGenerate structured Markdown incident runbooks from alerts and incident classes.
nikhillinitDetect and prioritize technical debt with configurable thresholds and SQALE metrics.
PostHogForward PostHog logs to Datadog using OTLP endpoints.
