All skills
redis avatar

/redis-observability

@ef0caa1 official
by redisredis/agent-skills163 stars
30

Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO, MEMORY DOCTOR, CLIENT LIST, FT.PROFILE), and when to use the Redis Insight GUI. Use when setting up monitoring or alerts for a Redis instance, diagnosing a performance regression, profiling a slow FT.SEARCH query, or wiring Redis metrics into Prometheus, Datadog, or similar.

Use this Skill: https://skilld.dev/gh/redis/agent-skills/redis-observability

This session only. Nothing lands on disk.

referencesmetrics.md

≈305 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Monitor Key Redis Metrics

Track these metrics to catch issues before they impact users.

Metric What It Tells You Alert When
used_memory Current memory usage > 80% of maxmemory
connected_clients Number of connections Sudden spikes or drops
blocked_clients Clients waiting on blocking ops > 0 sustained
instantaneous_ops_per_sec Current throughput Significant drops
keyspace_hits/misses Cache hit ratio Hit ratio < 80%
rejected_connections Connection limit issues > 0
rdb_last_save_time Last persistence snapshot Too old

Correct: Export metrics to your monitoring system.

# Get key metrics
info = redis.info()
print(f"Memory: {info['used_memory_human']}")
print(f"Connections: {info['connected_clients']}")
print(f"Ops/sec: {info['instantaneous_ops_per_sec']}")
print(f"Hit ratio: {info['keyspace_hits'] / (info['keyspace_hits'] + info['keyspace_misses']) * 100:.1f}%")

Redis Insight: Use Redis Insight for visual monitoring, query profiling, and debugging. It includes Redis Copilot for natural language queries.

Reference: Redis Insight

Source: SKILL.md on GitHub

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill provides instructions and Python code snippets for monitoring Redis performance and diagnosing issues using built-in commands like INFO and SLOWLOG. It is well-documented and exclusively uses official Redis resources.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at ef0caa1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 4 months ago
metadata
{
  "author": "Redis, Inc.",
  "version": "0.1.0"
}
  • Performance
  • redis
  • monitoring
  • observability
  • metrics
  • incident-response
  • slowlog
  • memory
  • prometheus
  • datadog

README badge

README badge for redis/agent-skills/redis-observability

Identifies which Redis metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to run during incidents (SLOWLOG, INFO, MEMORY DOCTOR, CLIENT LIST, FT.PROFILE), and when to use Redis Insight. Apply when setting up alerts, diagnosing performance regressions, or profiling slow queries.

Generated from the current SKILL.md.

Does this skill cover setting up Prometheus or Datadog exporters?
No. The skill identifies which metrics to export (used_memory, hit ratio, ops/sec, etc.) and which commands to run, but does not include exporter configuration or integration code.
Can I use this skill to profile slow FT.SEARCH queries?
Yes. The skill covers FT.PROFILE and FT.INFO commands for diagnosing slow search queries, and mentions Redis Insight as a GUI option for interactive profiling.
Does this skill apply to Redis Cluster or only standalone instances?
The skill focuses on core observability principles (monitoring metrics, using built-in commands) that apply broadly, but does not explicitly address Cluster-specific considerations.
What's the difference between this skill and Redis Insight?
This skill is reference material on what to monitor and which commands to run; Redis Insight is a GUI tool. The skill recommends Insight for interactive debugging during development or incidents, but emphasizes exporting metrics to your monitoring system as the primary approach.

Generated from the current SKILL.md. These answers refresh after source changes.