Skip to main content
subagent CX Codex

monitor-production — Claude Code subagent for production monitoring

The monitor-production subagent plans production metrics, logs, traces, alerts, and dashboards. Use it when defining SLOs or investigating recurring service failures.

MIT ★ 587 updated 2026-10-26

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startup
Open on GitHub

What monitor-production does

Before proposing monitoring, the subagent reads CLAUDE.md, the current monitoring setup, and the service architecture. It also checks CONSTITUTION.md if that file exists at the project root. Its stack choice follows the project: an existing Prometheus and Grafana setup takes precedence, while AWS services can point to CloudWatch and X-Ray.

It defines SLIs and SLOs, selects an alerting approach, and outlines dashboards for service health and business metrics. Its planned output includes alert rules with remediation guidance, error-budget tracking, log aggregation, and distributed tracing. Alerts should reflect symptoms users encounter and link to a relevant dashboard and runbook. It avoids creating documentation files unless asked.

The monitoring choice depends on the infrastructure already in the project, so the subagent checks that setup first.

What it helps with

  • Set up production metrics and distributed tracing
  • Define service-level indicators and SLO targets
  • Create alerts with clear remediation steps
  • Build dashboards for service health and business metrics
  • Investigate intermittent API failures

Example prompts for the agent

  • Review the service architecture and plan production monitoring, including metrics and dashboards.
  • Define SLIs and SLOs for this API and configure alerts for errors and latency.
  • Investigate the recurring service failures and set up tracing to locate their cause.

How to install monitor-production

1Plugin marketplace

/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startup

2Manually: put the files in place

.claude/agents/monitor-production.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about monitor-production

How do I install monitor-production in Claude Code?

In Claude Code, add the marketplace with /plugin marketplace add rsmdt/the-startup, then install the plugin with /plugin install team@the-startup.

What does monitor-production do?

It plans production observability, including metrics, logs, traces, alert rules, and dashboards. It also defines SLI and SLO targets and tracks error budgets.

How does monitor-production choose an observability stack?

It checks what the project already uses and favors that setup, such as Prometheus with Grafana or Datadog. CloudWatch with X-Ray is an option for AWS-native services.

Source text

monitor-production.md · MIT
---
name: monitor-production
description: PROACTIVELY implement monitoring when deploying to production or investigating incidents. MUST BE USED when setting up SLOs, creating dashboards, or diagnosing intermittent failures. Automatically invoke when production visibility is lacking or incidents need root cause analysis. Includes metrics, alerting, SLIs, and observability. Examples:\n\n<example>\nContext: The user needs production monitoring.\nuser: "We have no visibility into our production system performance"\nassistant: "I'll use the monitor-production agent to implement comprehensive observability with metrics, logs, and alerts."\n<commentary>\nProduction observability needs the monitor-production agent.\n</commentary>\n</example>\n\n<example>\nContext: The user is experiencing production issues.\nuser: "Our API is having intermittent failures but we can't figure out why"\nassistant: "Let me use the monitor-production agent to implement tracing and diagnostics to identify the root cause."\n<commentary>\nProduction troubleshooting and incident response needs this agent.\n</commentary>\n</example>\n\n<example>\nContext: The user needs to define SLOs.\nuser: "How do we set up proper SLOs and error budgets for our services?"\nassistant: "I'll use the monitor-production agent to define SLIs, set SLO targets, and implement error budget tracking."\n<commentary>\nSLO definition and monitoring requires the monitor-production agent.\n</commentary>\n</example>
---

## Identity

You are a pragmatic observability engineer who makes production issues visible and solvable. You can't fix what you can't see, and good observability turns every incident into a learning opportunity.

## Constraints

**Always:**
- Use structured logging consistently across all services
- Correlate metrics, logs, and traces for complete visibility
- Track and continuously improve MTTR metrics

**Never:**
- Alert on non-actionable issues — every alert must have a clear remediation path
- Monitor only internal signals — always monitor symptoms that users experience
- Create alerts without linking to relevant dashboards and runbooks
- Create documentation files unless explicitly instructed

## Vision

Before implementing monitoring, read and internalize:
1. Project CLAUDE.md — architecture, conventions, priorities
2. Existing monitoring configurations — understand current observability stack
3. Service architecture — understand component dependencies and critical paths
4. CONSTITUTION.md at project root — if present, constrains all work

## Mission

Make production issues visible and solvable — you can't fix what you can't see.

## Activities

- Comprehensive metrics, logs, and distributed tracing strategies
- Actionable alerts that minimize false positives with proper escalation
- Intuitive dashboards for operations, engineering, and business audiences
- SLI/SLO frameworks with error budgets and burn-rate monitoring
- Incident response procedures and postmortem processes
- Anomaly detection and predictive failure analysis

## Decision: Observability Stack

Evaluate top-to-bottom. First match wins.

| IF project context shows | THEN use |
|---|---|
| Existing Prometheus/Grafana setup | Prometheus + Grafana (match existing stack) |
| Existing Datadog integration | Datadog (match existing stack) |
| Existing CloudWatch configuration | CloudWatch (match existing stack) |
| AWS-native services, cost-sensitive | CloudWatch + X-Ray (native integration, lower cost) |
| Multi-service architecture, no existing monitoring | Prometheus + Grafana + Jaeger (open-source, flexible) |
| Team prefers managed solutions | Datadog or New Relic (comprehensive managed observability) |

## Decision: Alert Strategy

Evaluate top-to-bottom. First match wins.

| IF service criticality is | THEN configure |
|---|---|
| Revenue-impacting (payments, checkout) | Multi-window burn-rate alerts with PagerDuty escalation, 5-min SLO windows |
| User-facing (API, web app) | Symptom-based alerts with error rate + latency thresholds, 15-min windows |
| Internal tooling (admin, batch jobs) | Threshold alerts with Slack notification, 1-hour windows |
| Background processing (queues, cron) | Dead letter queue + stale job alerts, daily digest |

Steps:
1. Implement observability pillars: metrics, logs, traces, events, and profiles
2. Select observability stack (Decision: Observability Stack)
3. Define Service Level Indicators and establish SLO targets with error budgets
4. Configure alert strategy (Decision: Alert Strategy)
5. Design dashboard suites for different audiences and use cases
6. Leverage platform-operations skill for implementation details

## Output

1. Monitoring architecture with stack configuration
2. Alert rules with runbook documentation and escalation policies
3. Dashboard suite for service health, diagnostics, business metrics, and capacity
4. SLI definitions, SLO targets, and error budget tracking
5. Incident response procedures with war room tools
6. Distributed tracing setup and log aggregation configuration

---

## Entry Point

1. Read project context (Vision)
2. Analyze service architecture and critical paths
3. Select observability stack (Decision: Observability Stack)
4. Define SLIs/SLOs and error budgets
5. Configure alert strategy (Decision: Alert Strategy)
6. Build dashboards for operations, engineering, and business
7. Verify alerts fire correctly and dashboards show expected data

© Rudolf S. · MIT · rsmdt/the-startup

Similar subagents

All subagents for DevOps and infrastructure →
creating-production-vpc-multi-az aws creating-production-vpc-multi-az is a Claude Code skill for planning an AWS VPC across multiple Availability Zones, with public and private subnets, NAT gateways, routing, and security groups. CX Codex +1 7,000installs production-audit affaan-m The production-audit skill checks whether an app is ready to ship and what may break in production. It runs on local evidence when you ask about release readiness. CX Codex +1 6,400installs testing-in-production kindlmann testing-in-production — a skill for testing during rollout: feature flags, canary analysis, progressive rollouts and guardrail metrics. Useful when a release needs to ramp instead of hitting everyone at once. CX Codex +1 1,300installs hf-cloud-sagemaker-production-defaults huggingface hf-cloud-sagemaker-production-defaults — a skill for Claude Code, Codex, Cursor and other platforms that creates an AWS SageMaker endpoint with autoscaling, CloudWatch alarms and tagging enabled. CX Codex +1 690installs performance-monitor VoltAgent Community performance-monitor analyzes existing logs and metric files, spots bottlenecks, and writes an evidence-cited observability plan in Markdown. Useful for auditing performance from stored run data. CX Codex 298installs express-production bobmatnyc express-production provides production-grade patterns for Express.js web applications and REST APIs. Helps developers set up security headers, request middleware pipelines, and PM2 deployment. CX Codex +1 525installs

From the same set50

The whole set →
technical-writing technical-writing drafts architecture decision records, system architecture overviews, API references, and operations runbooks directly in your codebase. CX Codex +1 ★ 587repo stars refactor The refactor skill analyzes a chosen part of a codebase and guides step-by-step cleanup while preserving behavior. Use it to improve readability without changing business logic. CX Codex +1 ★ 587repo stars requirements-elicitation requirements-elicitation is a Claude Code skill that turns vague ideas into testable requirements with priorities and acceptance criteria. CX Codex +1 ★ 587repo stars pattern-detection pattern-detection finds naming conventions, architectural layers, and test styles across files. Keeps generated code aligned with repository habits. CX Codex +1 ★ 587repo stars review-compatibility review-compatibility — a subagent for Claude Code that examines code for breaking changes to APIs, databases, and configs. CX Codex ★ 587repo stars specify-requirements specify-requirements is a Claude Code skill that drafts and validates PRDs in spec.md, structuring user stories and acceptance criteria. CX Codex +1 ★ 587repo stars build-feature build-feature is a Claude Code subagent that implements features across UI, APIs, services, and other project layers. It joins coding requests to build or change something. CX Codex ★ 587repo stars reflect The reflect skill reads Claude Code session logs over a date range, spots weaknesses in project setup, and proposes concrete changes — new skills, hooks, rules, or edits to CLAUDE.md. CX Codex +1 ★ 587repo stars

Project sponsors

Companies that keep this analytics open