Data Systems
    Updated May 2026
    Memcached logo

    Memcached Monitoring

    Monitor Memcached `get_hits`/`get_misses` hit ratio, `evictions`, `bytes` used vs `limit_maxbytes`, `curr_connections`, and `listen_disabled_num` in real time — via the native `stats` command.

    Start Free TrialView Docs

    Why monitor Memcached?

    Memcached is the lean cache when you don't need Redis's data structures — WordPress object cache, PHP sessions, Django/Rails query results. When evictions climb or memory fills, your DB gets hammered by what used to be cache hits. Monitoring catches eviction storms before they cascade into database overload.

    Auto-discovery via Xitogent — no manual configuration required
    Real-time memory usage and allocation metrics
    Track hit/miss ratios and cache effectiveness
    Monitor active connections and connection rates
    Eviction rate and slab utilization tracking
    Items stored and reclaimed monitoring
    Works on both Linux and Windows servers
    1-minute metric collection intervals
    What is Memcached monitoring?

    Memcached monitoring, explained

    Memcached monitoring catches eviction storms, memory pressure, connection saturation, and degrading hit ratios before they cause uncached requests to hammer your database. For WordPress object cache, PHP sessions, Django/Rails query result caching, and AWS ElastiCache Memcached deployments, per-node visibility is what separates a 60-second alert from finding your DB pegged at 100% CPU at 3am. Xitoring auto-discovers your Memcached, reads stats on a 1-minute interval, and routes alerts to Slack, PagerDuty, Telegram, or your existing on-call.

    Metrics

    What we monitor

    Used Memory

    Total memory currently allocated for cached items.

    Max Memory

    Maximum memory limit configured for the Memcached instance.

    Hit Rate

    Percentage of successful cache lookups vs misses, indicating cache effectiveness.

    Evictions

    Number of items evicted to make room for new data.

    Current Connections

    Number of currently open client connections.

    Items Stored

    Total number of items currently stored in cache.

    Get/Set Ratio

    Ratio of get to set commands, indicating read/write balance.

    Bytes Read/Written

    Total network throughput for the Memcached instance.

    CAS Hits/Misses

    Check-and-set operation success rates for concurrent updates.

    Slab Utilization

    Memory allocation efficiency across slab classes.

    Triggers & Alerts

    Configurable alert triggers

    Set up custom triggers in your dashboard to get notified the moment Memcached metrics cross your defined thresholds.

    Memcached monitoring trigger configuration dashboard

    Memory Usage

    critical

    Fires when Memcached memory consumption approaches the configured limit, risking evictions.

    Hit Rate Drop

    warning

    Alerts when cache hit rate drops below threshold, indicating cache inefficiency or working set changes.

    Eviction Rate

    critical

    Fires when eviction rate spikes, meaning Memcached is actively removing data to stay within memory limits.

    Connection Count

    warning

    Triggers when client connections exceed the threshold, indicating potential connection leaks.

    Items Reclaimed

    warning

    Alerts when expired items are being reclaimed at a high rate, suggesting TTL misconfiguration.

    01

    Importance of Memcached Monitoring

    Memcached silently powers your application's performance layer. Without monitoring, memory exhaustion, eviction storms, and connection leaks can degrade your entire application stack before anyone notices.

    • Detect memory pressure before evictions impact application performance
    • Monitor cache hit rates to ensure optimal response times
    • Track eviction patterns to right-size your memory allocation
    • Identify connection leaks from application clients
    • Ensure consistent cache performance across distributed nodes
    Memcached cache performance monitoring dashboard
    Memcached slab utilization and memory analytics
    02

    Why Choose Xitoring

    Xitoring delivers enterprise-grade Memcached monitoring with zero-config setup. Our lightweight agent auto-discovers your Memcached instances, starts collecting metrics in under 60 seconds, and integrates with your existing notification channels.

    • One-command install — no complex YAML or config files
    • 15+ global monitoring nodes for low-latency checks
    • Unified dashboard for servers, caches, and uptime
    • Flexible alerting via Slack, PagerDuty, Telegram & more
    • Historical data retention for capacity planning & audits
    Xitoring Memcached cluster monitoring overview
    Alert notification channels configuration
    Use cases

    Common Memcached monitoring scenarios

    Where Memcached typically runs today — and what could go wrong if no one's watching.

    Speeding up WordPress and PHP sites

    Memcached keeps WordPress and PHP sites fast by remembering the results of repeated work. When the cache stops paying off, the site quietly gets slow under load. We surface that early so visitors and conversions aren't quietly affected.

    Speeding up web apps and APIs

    Web apps put their most expensive results in the cache so they don't have to compute them on every request. When the cache fills up or starts thrashing, the original work comes flooding back to the database. We catch the moment the cache stops protecting your app so the team can step in before users feel it.

    Managed cache running in the cloud

    Cloud providers handle the servers, but they don't tell you when your own use of the cache is becoming inefficient — running out of memory, hitting connection limits, or evicting useful data. We close that gap so you keep control of cost and performance.

    Before you start

    Prerequisites for Memcached

    Make sure you've got these in place — most installs are a 60-second job once they are.

    • Memcached 1.6.x (current) or 1.4.x running on its configured port (default 11211)
    • Network reachability from Xitogent to the Memcached instance (telnet host 11211 + stats to verify)
    • stats command accessible (no AUTH required by default; SASL supported when enabled)
    Setup Guide

    Get started in minutes

    1

    Install Xitogent on your server

    If you haven't already, install the lightweight Xitogent monitoring agent on your server.

    curl -s https://xitoring.com/install.sh | sudo bash -s -- --key=YOUR_API_KEY
    2

    Ensure Memcached stats are accessible

    Xitogent uses the Memcached stats command to collect metrics. Verify your instance is reachable locally:

    echo 'stats' | nc localhost 11211 | head -10
    3

    Enable the Memcached integration

    Use the Xitoring dashboard or CLI to enable the Memcached integration. Xitogent will auto-detect your instance.

    sudo xitogent integrate
    4

    Configure alert thresholds (optional)

    Set custom thresholds for metrics like memory usage, hit rate, or eviction count to get notified when something needs attention.

    5

    Verify it's working

    Run this command on the server to confirm Xitogent picked up the integration. Fresh metrics will start streaming to your dashboard within ~30 seconds.

    sudo xitogent status
    Compare

    Considering alternatives?

    See how Xitoring stacks up against the alternatives for Memcached monitoring — flat pricing, deeper integrations, and one agent that covers your whole stack.

    See all comparisons

    Frequently asked questions

    What is Memcached monitoring?
    Memcached monitoring is the continuous collection of cache server metrics from the native `stats` command — hit ratio (`get_hits`/`get_misses`), memory usage (`bytes` vs `limit_maxbytes`), evictions, connection counts, command rates, network throughput, slab utilization — combined with alerting when those metrics breach thresholds. It's how teams catch eviction storms and connection-limit hits before they cause cache misses that hammer the database tier.
    How do I monitor Memcached hit ratio?
    Hit ratio = `get_hits / (get_hits + get_misses)` from the `stats` output. Target 90%+ for object cache and session store; below 70% means the cache isn't helping much (working set too large, TTLs too short, or cache stampede). Xitogent trends the ratio automatically and alerts when it drops below your baseline.
    What do high evictions mean in Memcached?
    `evictions` counts items removed to make room for new data when memory is full. Any sustained non-zero rate means `-m ` is too small for your working set — either raise `-m`, lower TTLs to age out stale data faster, or distribute across more Memcached nodes. `evicted_nonzero` is more interesting: it counts evictions of items that still had time to live, which means hot data is being thrown away.
    How do I detect Memcached memory pressure?
    Compare `bytes` (current memory used by items) against `limit_maxbytes` (the `-m` config) — above 95% means you're seconds away from eviction. On AWS ElastiCache, watch the `UnusedMemory` CloudWatch metric (inverse — alert when it drops below 10% of total). Pair with `evictions` rate to confirm whether you're in active eviction or just close to the limit.
    How do I monitor Memcached connection limits?
    `listen_disabled_num` counts how many times Memcached temporarily stopped accepting new connections because `-c ` was hit (default 1024). Any non-zero rate means clients are being rejected. Either raise `-c` (and OS file descriptors with `ulimit -n`) or fix the app-side connection leak. Monitor alongside `curr_connections` to confirm whether you're close to the ceiling.
    Memcached vs Redis — which to choose?
    Memcached wins for pure ephemeral key/value caching: simpler, faster per-op, lower memory overhead, multi-threaded by default, native scaling via consistent hashing in the client. Redis wins when you need data structures (sorted sets, hashes, streams), persistence (RDB/AOF), pub/sub, Lua scripting, or replication. Many sites use both: Memcached for object cache + sessions, Redis for queues + leaderboards.
    How do I run `stats` against Memcached?
    `telnet 11211` (or `nc 11211`), then type `stats`. You'll see ~50 `STAT ` lines. `stats slabs` shows per-slab-class memory usage; `stats items` shows per-class item counts and expiration data. Run `flush_all` to nuke all keys (dev only). Xitogent runs the same `stats` automatically every minute and graphs the output.
    How do I monitor a Memcached cluster?
    Memcached doesn't have built-in clustering — sharding is client-side via consistent hashing (libmemcached, mcrouter, twemproxy). Monitor each node separately with Xitogent. For AWS ElastiCache Memcached clusters, the agent runs against the cluster discovery endpoint and tracks per-node metrics. For Facebook-scale deployments using mcrouter as a proxy, monitor mcrouter health alongside each backend Memcached.
    What Memcached versions are supported?
    Memcached 1.4 and later are fully supported, including the current 1.6.x line. 1.6.x adds `extstore` (flash/SSD value tier for working sets larger than RAM), the meta protocol (compact text commands superseding the binary protocol), TLS support, `slab_automove` mode 2 (aggressive per-eviction page reassignment), and `lru_crawler`/`lru_maintainer` background reclaimers. Xitogent surfaces metrics from all of them when enabled.

    Start monitoring Memcached today

    Set up in under 60 seconds. No credit card required. Full metrics from day one.

    Start Free Trial

    Keep exploring

    Related Integrations