Plugin: python.d.plugin Module: memcached
Monitor Memcached metrics for proficient in-memory key-value store operations. Track cache hits, misses, and memory usage for efficient data caching.
It reads server response to stats command (stats interface).
This collector is supported on all platforms.
This collector supports collecting metrics from multiple instances of this integration, including remote instances.
If no configuration is given, collector will attempt to connect to memcached instance on
The default configuration for this integration does not impose any limits on data collection.
The default configuration for this integration is not expected to impose a significant performance impact on the system.
Metrics grouped by scope.
The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.
Per Memcached instance
These metrics refer to the entire monitored application.
This scope has no labels.
|current, rejected, total
|hits, misses, bad value
The following alerts are available:
|cache memory utilization
|average rate the cache fills up (positive), or frees up (negative) space over the last hour
|estimated time the cache will run out of space if the system continues to add data at the same rate as the past hour
No action required.
The configuration file name for this integration is
You can edit the configuration file using the
edit-config script from the
Netdata config directory.
cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config python.d/memcached.conf
There are 2 sections:
- Global variables
- One or more JOBS that can define multiple different instances to monitor.
The following options can be defined globally: priority, penalty, autodetection_retry, update_every, but can also be defined per JOB to override the global values.
Additionally, the following collapsed table contains all the options that can be configured inside a JOB definition.
Every configuration JOB starts with a
job_name value which will appear in the dashboard, unless a
name parameter is specified.
|the host to connect to.
|the port to connect to.
|Sets the default data collection frequency.
|Controls the order of charts at the netdata dashboard.
|Sets the job re-check interval in seconds.
|Indicates whether to apply penalty to update_every in case of failures.
|Job name. This value will overwrite the
job_name value. JOBS with the same name are mutually exclusive. Only one of them will be allowed running at any time. This allows autodetection to try several alternatives and pick the one that works.
An example configuration for localhost.
An example configuration for localipv4.
An example configuration for localipv6.
To troubleshoot issues with the
memcached collector, run the
python.d.plugin with the debug option enabled. The output
should give you clues as to why the collector isn't working.
Navigate to the
plugins.ddirectory, usually at
/usr/libexec/netdata/plugins.d/. If that's not the case on your system, open
netdata.confand look for the
Switch to the
sudo -u netdata -s
python.d.pluginto debug the collector:
./python.d.plugin memcached debug trace
Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.