Our Memcached integration collects and sends inventory and metrics from your Memcached instance to our platform, where you can aggregate and visualize key performance metrics. We collect data at both instance and slab levels.
Read on to install the integration, and to see what data we collect.
Compatibility and requirements [#comp-req]
Our integration is compatible with Memcached 1.4 or higher.
If Memcached is not running on Kubernetes or Amazon ECS, you must install the infrastructure agent on a host that's running Memcached. Otherwise:
- If running on Kubernetes, see these requirements.
- If running on ECS, see these requirements.
Quick start [#quick]
Instrument your Memcached instance quickly and send your telemetry data with guided install. Our guided install creates a customized CLI command for your environment that downloads and installs the New Relic CLI and the infrastructure agent.
Ready to get started? Click one of these button to try it out.
Our guided install uses the infrastructure agent to set up the Memcached integration. Not only that, it discovers other applications and log sources running in your environment and then recommends which ones you should instrument.
The guided install works with most setups. But if it doesn't suit your needs, you can find other methods below to get started monitoring your MySQL instance.
Install and activate [#install]
To install the Memcached integration, follow the instructions for your environment:
{ ' ' }
Additional notes:
- **Advanced:**Integrations are also available in [tarball format](/docs/integrations/host-integrations/installation/install-host-integrations-built-new-relic#tarball) to allow for install outside of a package manager.
- **On-host integrations do not automatically update.**For best results, regularly [update the integration package](/docs/integrations/host-integrations/installation/update-infrastructure-host-integration-package) and [the infrastructure agent](/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent).
Configure the integration [#config]
An integration's YAML-format configuration is where you can place required login credentials and configure how data is collected. Which options you change depend on your setup and preference.
There are several ways to configure the integration, depending on how it was installed:
- If enabled via Kubernetes: see Monitor services running on Kubernetes.
- If enabled via Amazon ECS: see Monitor services running on ECS.
- If installed on-host: edit the config in the integration's YAML config file,
memcached-config.yml
.
The configuration file has common settings used by all of our integrations, such as interval
, timeout
, and inventory_source
. For more on these common settings, see our configuration properties list.
If you're still using our legacy configuration/definition files, see the standard configuration format for help.
Specific settings related to Memcached are defined using the env
section of the configuration file. These settings control the connection to your Memcached instance as well as other security settings and features.
Configuration options are below. For a better sense of how this works in practice, see our example config file.
Memcached instance settings [#instance-settings]
The Memcached integration collects both Metrics(M) and Inventory(I) information. Check the
The values for these settings can be defined in several ways:
- Add the value directly in the config file.
- Replace the values from environment variables using the
{{}}
notation. This requires infrastructure agent version 1.14.0 or higher. Read more here or see example below. - Use secrets management to protect sensitive information, such as passwords, from being exposed in plain text in the configuration file. For more information, see how to use secrets management.
Labels/custom attributes [#labels]
You can also decorate your metrics using labels. Labels allow you to add key/value pair attributes to your metrics. You can use them to query, filter, or group your metrics.
Our default sample configuration file includes examples of labels, but you can remove, modify, or add new ones of your choice.
labels: env: production role: memcached
Example configuration [#example-config]
Example memcached-config.yml
file configuration:
For more about the general structure of on-host integration configuration, see our integration configuration overview.
Find and use data [#find-and-use]
Data from this service is reported to an integration dashboard.
Metrics are attached to these event types:
MemcachedSample
MemcachedSlabSample
You can query this data for troubleshooting purposes or to create custom charts and dashboards.
For more on how to find and use your data, see Understand integration data.
Metric data [#metrics]
The Memcached integration collects the following metric data attributes.
Memcached sample metrics [#memcached-sample]
These attributes are attached to this MemcachedSample
event type:
Memcached slab sample metrics [#memcached-slab-sample]
These attributes are attached to the MemcachedSlabSample
event type:
Inventory data [#inventory]
The Memcached integration captures the configuration parameters of the memcached instance. The data is available on the Inventory page, under the
The integration captures data for the following Memcached configuration parameters: