The Agent's Memcache check lets you track Memcache's memory use, hits, misses, evictions, fill percent, and much more.
The Memcache check is included in the Datadog Agent package, so you don't need to install anything else on your Memcache servers.
Follow the instructions below to configure this check for an Agent running on a host. For containerized environments, see the Containerized section
-
Edit the
mcache.d/conf.yaml
file, in theconf.d/
folder at the root of your Agent's configuration directory. See the sample mcache.d/conf.yaml for all available configuration options:init_config: instances: ## @param url - string - required ## url used to connect to the Memcached instance. # - url: localhost
-
Restart the Agent to begin sending Memcache metrics to Datadog.
For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.
Parameter | Value |
---|---|
<INTEGRATION_NAME> |
mcache |
<INIT_CONFIG> |
blank or {} |
<INSTANCE_CONFIG> |
{"url": "%%host%%","port": "11211"} |
Available for Agent versions >6.0
-
Add this configuration block to your
mcache.d/conf.yaml
file to start collecting your Memcached Logs:logs: - type: file path: /var/log/memcached.log source: memcached service: mcache
Change the
path
andservice
parameter values and configure them for your environment. -
Restart the Agent to validate these changes.
Run the Agent's status
subcommand and look for mcache
under the Checks section.
See metadata.csv for a list of metrics provided by this check.
The check only collects memcache.slabs.*
metrics if you set options.slabs: true
in mcache.d/conf.yaml
. Likewise, it only collects memcache.items.*
metrics if you set options.items: true
.
The Mcache check does not include any events.
memcache.can_connect
:
Returns CRITICAL
if the Agent cannot connect to memcache to collect metrics, otherwise OK
.
Need help? Contact Datadog support.