From arn-infra
This skill should be used when the user says "set up monitoring", "arn infra monitor", "infra monitor", "configure monitoring", "set up observability", "add logging", "configure alerting", "set up alerts", "infrastructure monitoring", "add metrics", "set up cloudwatch", "configure grafana", "observability setup", "logging setup", "alerting setup", "health checks", "monitor infrastructure", "arn-infra-monitor", "set up cloud monitoring", "configure notifications", "prometheus", "datadog", "new relic", "sentry", or wants to set up logging, metrics collection, and alerting for their deployed infrastructure.
npx claudepluginhub appsvortex/arness --plugin arn-infraThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.
Set up observability for deployed infrastructure: structured logging, metrics collection, and alerting. This skill recommends an observability stack based on the configured cloud provider, generates IaC for monitoring resources, and configures basic health-check-based alerts.
This skill focuses on initial monitoring setup and critical alerts. It does NOT create full monitoring dashboards (out of scope per spec). For ongoing monitoring and alerting customization, refer users to their provider's monitoring console.
Read ## Arness from the project's CLAUDE.md. If no ## Arness section exists or Arness Infra fields are missing, inform the user: "Arness Infra is not configured for this project yet. Run /arn-infra-wizard to get started — it will set everything up automatically." Do not proceed without it.
Check the Deferred field. If Deferred: yes, inform the user: "Infrastructure is in deferred mode. Monitoring setup is not available until infrastructure is fully configured. Run /arn-infra-assess to un-defer." Stop.
Extract:
~/.arness/user-profile.yaml (or .claude/arness-profile.local.md if it exists — project override takes precedence). Apply the experience derivation mapping from ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-ensure-config/references/experience-derivation.md. If no profile exists, check for legacy Experience level in ## Arness as fallback.providers.md for per-provider detailsenvironments.mdtooling-manifest.jsonactive-resources.json for checking deployed resource state (if available from prior deployments)Scan for existing monitoring configurations:
Glob **/cloudwatch*.tf
Glob **/monitoring*.tf
Glob **/alerting*.tf
Glob **/datadog*.tf
Glob **/grafana*.tf
Glob **/prometheus*.yml
Glob **/alertmanager*.yml
Glob docker-compose*.yml
Check deployed resources (if available):
Read <resource-manifest-path>
If existing monitoring is detected: Present: "I found existing monitoring configuration: [list]. I can extend this with additional alerts and logging."
If no monitoring is detected: Continue to Step 2 for fresh monitoring setup.
Read the local override or plugin default for
observability-stack-guide.md.
Based on the configured provider(s) and experience level, recommend a monitoring approach:
Expert: Present all options: "Here are the observability options for your [provider] setup:
Native monitoring:
Third-party options:
Which approach do you prefer?"
Intermediate: Present the recommended stack: "For [provider], I recommend:
This uses your cloud provider's built-in tools, so there are no additional services to manage. Would you like to proceed, or would you prefer a third-party solution?"
Beginner: Make the recommendation directly: "I'll set up monitoring using [provider's native tools]. This gives you logging, metrics, and alerts without any extra services or costs beyond your cloud provider."
Stack selection per provider:
Guide the setup of structured logging for the deployment:
Application logging:
Infrastructure logging:
Log retention per environment:
| Environment | Retention | Rationale |
|---|---|---|
| Dev | 7 days | Cost optimization |
| Staging | 30 days | Debugging window |
| Production | 90 days | Compliance (SOC 2 minimum) |
Set up metrics collection for key infrastructure components:
Core metrics to collect:
Custom metrics (optional for expert users):
Read the local override or plugin default for
alerting-patterns.md.
Set up alerts for critical conditions:
Essential alerts (configured for all experience levels):
| Alert | Metric | Threshold | Severity |
|---|---|---|---|
| Service down | Health check | 3 consecutive failures | Critical |
| High error rate | HTTP 5xx rate | > 5% of requests for 5 min | Critical |
| High CPU | CPU utilization | > 80% for 10 min | Warning |
| High memory | Memory utilization | > 85% for 10 min | Warning |
| Disk space | Disk usage | > 80% for 15 min | Warning |
| High latency | Response time p99 | > 1s for 5 min | Warning |
| Critical latency | Response time p99 | > 3s for 5 min | Critical |
Notification channels:
Ask (using AskUserQuestion):
"Where should alerts be sent?"
Options:
Expert: Allow full customization of thresholds, metrics, and notification channels per alert.
Intermediate: Present defaults and allow adjustments: "Here are the recommended alert thresholds. Would you like to adjust any?"
Beginner: Apply defaults: "I'll set up alerts for the most critical conditions. You'll receive notifications at [chosen channel] when your services need attention."
Invoke the arn-infra-specialist agent via the Task tool with:
--- MONITORING CONTEXT --- Observability stack: [chosen stack] Provider: [provider] Environments: [list] Deployed resources: [from resource manifest, or "not yet deployed"] --- END MONITORING CONTEXT ---
--- LOGGING CONFIGURATION --- Log format: structured (JSON) Log destinations: [provider-native service] Retention: [per-environment retention settings] Infrastructure logs: [CloudTrail/Audit Logs enabled] --- END LOGGING CONFIGURATION ---
--- METRICS CONFIGURATION --- Core metrics: CPU, memory, disk, network, request count, error rate, latency Custom metrics: [any user-specified custom metrics] --- END METRICS CONFIGURATION ---
--- ALERTING CONFIGURATION --- [For each alert:] Alert name: [name] Metric: [metric source] Threshold: [value and duration] Severity: [critical | warning] Notification channel: [channel type and target] --- END ALERTING CONFIGURATION ---
--- INSTRUCTIONS --- Generate IaC for monitoring resources:
For each environment:
Follow these rules:
Present the generated monitoring configuration for user approval:
"Here is the monitoring setup:
Observability stack: [stack] Logging: [log service] with [retention] retention Metrics: [count] core metrics tracked Alerts: [count] alerts configured Notification channel: [channel]
[For each generated file:] [filename]:
[generated content]
Ask (using AskUserQuestion):
"How would you like to proceed with the monitoring configuration?"
Options:
Upon approval, write the files.
Monitoring Setup Summary:
Recommended next steps:
"Monitoring is configured. Here is the recommended path:
/arn-infra-deploy to deploy the monitoring configuration alongside your infrastructure/arn-infra-secrets if your monitoring requires API keys (e.g., Datadog, PagerDuty)Or run /arn-infra-wizard for the full guided pipeline."
## Arness config missing: Suggest running /arn-infra-wizard to get started. Stop./arn-infra-init to configure providers. Stop.