oc-monitoring-ops

Monitor application health, track errors, and manage incidents post-deployment.

Updated May 15, 2026
One-click install
npx skills add https://github.com/asfbay-bit/opchain-skills --skill oc-monitoring-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oc-monitoring-ops
Source: https://github.com/asfbay-bit/opchain-skills/tree/main/skills/oc-monitoring-ops
Command: npx skills add https://github.com/asfbay-bit/opchain-skills --skill oc-monitoring-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sentry, betterstack, pagerduty, telegram, slack, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill ensures post-deployment observability, proactive alerting, and incident management for your application, maintaining system health and reducing downtime.

Core Features & Use Cases

  • Uptime Monitoring: Monitor application availability and respond to downtime promptly.
  • Error Tracking: Capture and analyze errors for efficient debugging and resolution.
  • Alerting: Set up alerts for various metrics and take immediate action.
  • Incident Response: Manage incidents, execute runbooks, and restore service.
  • Dashboard and Reporting: Visualize metrics and generate operational reports.

Quick Start

Set up monitoring for your application using /oc-monitor setup.

Frequently Asked Questions about oc-monitoring-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up application health monitoring and alerting after a production deployment?

Application health monitoring and alerting can be configured using the setup command to track uptime, capture errors, and establish incident response protocols for your production environment.

What is the best way to manage production incidents and execute operational runbooks?

Incident management is handled by executing operational runbooks, tracking application errors, and restoring service through integrated alerting channels to reduce downtime and maintain system health.

Does this observability setup work with Sentry, PagerDuty, and Slack for error tracking and notifications?

Observability and incident management integrate directly with Sentry, PagerDuty, Slack, BetterStack, and Telegram to provide comprehensive error tracking, alerting, and operational visibility.

Can I visualize operational metrics and generate reports for my production environment?

Dashboard and reporting features visualize tracked metrics and generate operational reports, providing continuous observability and visibility into application health post-deployment.

Why do I need continuous observability for post-deployment system health?

Continuous observability ensures post-deployment system health by proactively monitoring application availability, tracking errors, and managing incidents to reduce unexpected downtime.

Are there limitations when using this approach for proactive alerting and uptime monitoring?

Proactive alerting and uptime monitoring require integrating external services like Sentry and PagerDuty, meaning operational visibility depends on the availability and configuration of those external dependencies.