Track cache hit rates, latency, and detect cache-related issues
Monitors cache performance metrics including hit rates, latency, and memory usage. Triggers automatically when cache operations are performed to detect issues like low hit rates, stampedes, or high latency.
/plugin marketplace add nexus-labs-automation/backend-observability/plugin install nexus-labs-automation-backend-observability@nexus-labs-automation/backend-observabilityThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Cache is performance-critical. Track hit rate, latency, and evictions.
| Metric | Type | Description |
|---|---|---|
cache.hits | Counter | Successful reads |
cache.misses | Counter | Reads that missed |
cache.gets.duration | Histogram | GET latency |
cache.evictions | Counter | Keys evicted |
cache.memory.used | Gauge | Memory consumption |
| Attribute | Example | Required |
|---|---|---|
cache.system | redis, memcached | Yes |
cache.operation | GET, SET | Yes |
cache.hit | true/false | Yes |
cache.key_prefix | user:* | Recommended (not full key!) |
hit_rate = cache.hits / (cache.hits + cache.misses)
| Issue | Detection | Fix |
|---|---|---|
| Low hit rate | <80% | Tune TTL, warm cache |
| Cache stampede | Many misses for same key | Distributed locks |
| High latency | p99 >10ms | Check network, value size |
| Memory pressure | memory >90% of max | Eviction policy, sizing |
Before GET: Start timer
After GET: Record duration, increment hits or misses, set cache.hit on span
references/platforms/{platform}/cache.mdUse when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.