datastore_diagnosis

Diagnosing Redis memory issues requires analyzing container stats and utilizing Redis commands to detect large keys and missing TTLs. This skill processes Prometheus metrics and container logs to identify the root causes of memory exhaustion and low cache hit rates.

The best way to find the cause of MySQL slow queries and lock waits is by examining database logs and connection pool metrics. This skill uses MySQL commands and Prometheus queries to detect slow queries, identify connection pool exhaustion, and pinpoint lock wait bottlenecks.

Monitoring message queue backlog and consumer delays involves querying Prometheus metrics and reviewing message broker logs. This skill detects accumulating message backlogs and identifies delayed consumers by analyzing throughput metrics and queue depth data from your monitoring system.

Yes, you need Prometheus metrics to diagnose database and cache performance issues with this skill. It requires access to container stats, logs, and Prometheus metrics alongside Redis and MySQL commands to successfully identify memory issues, slow queries, and message backlogs.

Yes, you can detect missing TTLs on Redis keys causing memory exhaustion. When a Redis server runs out of memory, this skill quickly identifies the root cause by running Redis commands to locate large keys and keys lacking an expiration time.