setup-monitoring-observability — Claude Code command: setup guide
This command inspects a project and guides setup for metrics, logs, tracing, and alerts. Choose one area or request the full observability stack.
npx claude-code-templates@latest --command setup/setup-monitoring-observabilityWhat setup-monitoring-observability does
The command checks project files to identify the application and infrastructure. It also searches for existing Prometheus, Grafana, and Jaeger configuration and scans src/ for logging references. Pass an argument to focus the work on metrics, logging, tracing, or a full stack.
Its instructions cover application and infrastructure metrics, centralized structured logs, distributed tracing, alerting, and dashboards. Integration options named in the command include Prometheus, Grafana, ELK Stack, Jaeger, DataDog, New Relic, and cloud-native solutions. It also calls for APM and analytics features. This is an instruction for Claude Code to configure observability, not a monitoring server by itself.
Use --metrics, --logging, --tracing, or --full-stack, or supply [monitoring-type]. The command relies on Read, Write, Edit, and Bash, so those tools need to be available to Claude Code.
What it helps with
- find existing monitoring configuration in a project
- collect application and infrastructure metrics
- centralize structured logs
- trace requests across services
- configure alerts and observability dashboards
Example prompts for the agent
- Set up application and infrastructure metrics with
/setup-monitoring-observability --metrics. - Add centralized logging by running
/setup-monitoring-observability --logging. - Configure the full observability stack with
/setup-monitoring-observability --full-stack.
How to install setup-monitoring-observability
1claude-code-templates
npx claude-code-templates@latest --command setup/setup-monitoring-observability2Manually: put the files in place
.claude/commands/setup-monitoring-observability.mdCall it with /setup-monitoring-observability. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/setup-monitoring-observability.mdCall it with /prompts:setup-monitoring-observability. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/setup-monitoring-observability.prompt.mdManually: put the files in place
.gemini/commands/setup-monitoring-observability.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about setup-monitoring-observability
How do I install setup-monitoring-observability in Claude Code?
Run npx claude-code-templates@latest --command setup/setup-monitoring-observability. The command file is located at .claude/commands/setup-monitoring-observability.md.
What does setup-monitoring-observability do?
It examines project configuration and guides Claude Code through setting up metrics, centralized logs, distributed tracing, and alerts. You can target one area or request the full stack.
Which arguments can I pass to the command?
Choose --metrics, --logging, --tracing, or --full-stack, or provide a [monitoring-type] value.
Source text
setup-monitoring-observability.md · MIT
--- allowed-tools: Read, Write, Edit, Bash argument-hint: "[monitoring-type] | --metrics | --logging | --tracing | --full-stack" description: Setup comprehensive monitoring and observability with metrics, logging, tracing, and alerting --- # Setup Monitoring & Observability Setup comprehensive monitoring and observability infrastructure: **$ARGUMENTS** ## Current Application State - Application type: @package.json or @requirements.txt (detect framework and services) - Existing monitoring: !`find . -name "*prometheus*" -o -name "*grafana*" -o -name "*jaeger*" | wc -l` - Infrastructure: @docker-compose.yml or @kubernetes/ or cloud platform detection - Logging setup: !`grep -r "winston\|logging\|console.log" src/ 2>/dev/null | wc -l` ## Task Implement production-ready monitoring and observability with comprehensive insights: **Monitoring Type**: Use $ARGUMENTS to focus on metrics, logging, distributed tracing, or complete observability stack **Observability Stack**: 1. **Metrics Collection** - Application metrics, infrastructure monitoring, business KPIs, custom dashboards 2. **Logging Infrastructure** - Centralized logging, structured logs, log aggregation, search capabilities 3. **Distributed Tracing** - Request tracing, performance analysis, bottleneck identification, service dependencies 4. **Alerting System** - Smart alerts, escalation policies, notification channels, incident management 5. **Performance Monitoring** - APM integration, real-user monitoring, synthetic monitoring, SLA tracking 6. **Analytics & Reports** - Usage analytics, performance trends, capacity planning, business insights **Platform Integration**: Prometheus, Grafana, ELK Stack, Jaeger, DataDog, New Relic, cloud-native solutions. **Production Features**: High availability, data retention policies, security controls, cost optimization. **Output**: Complete observability platform with real-time monitoring, intelligent alerting, and comprehensive analytics dashboards.
© davila7 · MIT · davila7/claude-code-templates
