Specify a webhook-driven task for OpenClaw
Describe event inputs, validation, deduplication, and intended actions before integration work.
Monitor database performance and health. Use when setting up monitoring, analyzing metrics, or troubleshooting database issues.
--- name: database-monitoring description: > Monitor database performance and health. Use when setting up monitoring, analyzing metrics, or troubleshooting database issues. --- # Database Monitoring ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Implement comprehensive database monitoring for performance analysis, health checks, and proactive alerting. Covers metrics collection, analysis, and troubleshooting strategies. ## When to Use - Performance baseline establishment - Real-time health monitoring - Capacity planning - Query performance analysis - Resource utilization tracking - Alerting rule configuration - Incident response and troubleshooting ## Quick Start Minimal working example: ```sql -- View current connections SELECT pid, usename, application_name, client_addr, state, query_start, state_change FROM pg_stat_activity WHERE state != 'idle' ORDER BY query_start DESC; -- Count connections per database SELECT datname, COUNT(*) as connection_count, MAX(EXTRACT(EPOCH FROM (NOW() - query_start))) as max_query_duration_sec FROM pg_stat_activity GROUP BY datname; -- Find idle transactions SELECT pid, usename, // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Connection Monitoring](references/connection-monitoring.md) | Connection Monitoring | | [Query Performance Monitoring](references/query-performance-monitoring.md) | Query Performance Monitoring | | [Table & Index Monitoring](references/table-index-monitoring.md) | Table & Index Monitoring | | [Performance Schema](references/performance-schema.md) | Performance Schema | | [InnoDB Monitoring](references/innodb-monitoring.md) | InnoDB Monitoring | | [PostgreSQL Monitoring Setup](references/postgresql-monitoring-setup.md) | PostgreSQL Monitoring Setup | | [Automated Monitoring Dashboard](references/automated-monitoring-dashboard.md) | Automated Monitoring Dashboard | ## Best Practices ### ✅ DO - Follow established patterns and conventions - Write clean, maintainable code - Add appropriate documentation - Test thoroughly before deploying ### ❌ DON'T - Skip testing or validation - Ignore error handling - Hard-code configuration values--- name: database-monitoring description: > Monitor database performance and health. Use when setting up monitoring, analyzing metrics, or troubleshooting database issues. --- # Database Monitoring ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Implement comprehensive database monitoring for performance analysis, health checks, and proactive alerting. Covers metrics collection, analysis, and troubleshooting strategies. ## When to Use - Performance baseline establishment - Real-time health monitoring - Capacity planning - Query performance analysis - Resource utilization tracking - Alerting rule configuration - Incident response and troubleshooting ## Quick Start Minimal working example: ```sql -- View current connections SELECT pid, usename, application_name, client_addr, state, query_start, state_change FROM pg_stat_activity WHERE state != 'idle' ORDER BY query_start DESC; -- Count connections per database SELECT datname, COUNT(*) as connection_count, MAX(EXTRACT(EPOCH FROM (NOW() - query_start))) as max_query_duration_sec FROM pg_stat_activity GROUP BY datname; -- Find idle transactions SELECT pid, usename, // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Connection Monitoring](references/connection-monitoring.md) | Connection Monitoring | | [Query Performance Monitoring](references/query-performance-monitoring.md) | Query Performance Monitoring | | [Table & Index Monitoring](references/table-index-monitoring.md) | Table & Index Monitoring | | [Performance Schema](references/performance-schema.md) | Performance Schema | | [InnoDB Monitoring](references/innodb-monitoring.md) | InnoDB Monitoring | | [PostgreSQL Monitoring Setup](references/postgresql-monitoring-setup.md) | PostgreSQL Monitoring Setup | | [Automated Monitoring Dashboard](references/automated-monitoring-dashboard.md) | Automated Monitoring Dashboard | ## Best Practices ### ✅ DO - Follow established patterns and conventions - Write clean, maintainable code - Add appropriate documentation - Test thoroughly before deploying ### ❌ DON'T - Skip testing or validation - Ignore error handling - Hard-code configuration values
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Includes source scripts; review them before use. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.