Memcached

The Memcached integration primarily collects cache-usage metrics, such as the number of items in a cache, the number of evictions, and the number of bytes stored. It also collects general performance metrics for CPU usage and network throughput.

For more information about Memcached, see the Memcached documentation.

Prerequisites

To collect Memcached telemetry, you must install the Ops Agent:

For metrics, install version 2.8.0 or higher.
For logs, install version 2.15.0 or higher.

This integration supports Memcached version 1.6.

Configure the Ops Agent for Memcached

Following the guide for Configuring the Ops Agent, add the required elements to collect telemetry from Memcached instances, and restart the agent.

Example configuration

The following command creates the configuration to collect and ingest telemetry for Memcached and restarts the Ops Agent.

set -e

# Create a back up of the existing file so existing configurations are not lost.
sudo cp /etc/google-cloud-ops-agent/config.yaml /etc/google-cloud-ops-agent/config.yaml.bak

# Configure the Ops Agent.
sudo tee /etc/google-cloud-ops-agent/config.yaml > /dev/null << EOF
metrics:
  receivers:
    memcached:
      type: memcached
  service:
    pipelines:
      memcached:
        receivers:
          - memcached
EOF

sudo service google-cloud-ops-agent restart
sleep 60

Collect logs

Memcached writes logs to syslog, which is captured by the Ops Agent by default. No additional user configuration is required.

Configure metrics collection

To ingest metrics from Memcached, you must create a receiver for the metrics that Memcached produces and then create a pipeline for the new receiver.

This receiver does not support the use of multiple instances in the configuration, for example, to monitor multiple endpoints. All such instances write to the same time series, and Cloud Monitoring has no way to distinguish among them.

To configure a receiver for your memcached metrics, specify the following fields:

Field	Default	Description
`collection_interval`	`60s`	A time duration value, such as `30s` or `5m`.
`endpoint`	`localhost:3306`	The URL, or Unix socket file path, for your Memcached server.
`type`		This value must be `memcached`.

What is monitored

The following table provides the list of metrics that the Ops Agent collects from the Memcached instance.

Metric type
Kind, Type Monitored resources	Labels
`workload.googleapis.com/memcached.bytes`
`GAUGE`, `INT64` gce_instance
`workload.googleapis.com/memcached.commands`
`CUMULATIVE`, `INT64` gce_instance	`command`
`workload.googleapis.com/memcached.connections.current`
`GAUGE`, `INT64` gce_instance
`workload.googleapis.com/memcached.connections.total`
`CUMULATIVE`, `INT64` gce_instance
`workload.googleapis.com/memcached.cpu.usage`
`CUMULATIVE`, `DOUBLE` gce_instance	`state`
`workload.googleapis.com/memcached.current_items`
`GAUGE`, `INT64` gce_instance
`workload.googleapis.com/memcached.evictions`
`CUMULATIVE`, `INT64` gce_instance
`workload.googleapis.com/memcached.network`
`CUMULATIVE`, `INT64` gce_instance	`direction`
`workload.googleapis.com/memcached.operations`
`CUMULATIVE`, `INT64` gce_instance	`operation` `type`
`workload.googleapis.com/memcached.threads`
`GAUGE`, `INT64` gce_instance

Verify the configuration

This section describes how to verify that you correctly configured the Memcached receiver. It might take one or two minutes for the Ops Agent to begin collecting telemetry.

To verify that the logs are ingested, go to the Logs Explorer and run the following query to view the Memcached logs:

resource.type="gce_instance"
log_id("syslog")
jsonPayload.message~='(systemd-memcached-wrapper|memcached)(\[[0-9]+\])*:'

To verify that the metrics are ingested, go to Metrics Explorer and run the following query in the MQL tab:

fetch gce_instance
| metric 'workload.googleapis.com/memcached.bytes'
| every 1m

View dashboard

To view your Memcached metrics, you must have a chart or dashboard configured. The Memcached integration includes one or more dashboards for you. Any dashboards are automatically installed after you configure the integration and the Ops Agent has begun collecting metric data.

You can also view static previews of dashboards without installing the integration.

To view an installed dashboard, do the following:

In the Google Cloud console, select Monitoring or click the following button:
Go to Monitoring
In the navigation pane, select Dashboards.
Select the Dashboard List tab.
Choose the Integrations category.
Click the name of the dashboard you want to view.

If you have configured an integration but the dashboard has not been installed, then check that the Ops Agent is running. When there is no metric data for a chart in the dashboard, installation of the dashboard fails. After the Ops Agent begins collecting metrics, the dashboard is installed for you.

To view a static preview of the dashboard, do the following:

In the Google Cloud console, select Monitoring or click the following button:
Go to Monitoring
In the navigation pane, select Integrations.
Click the Compute Engine deployment-platform filter.
Locate the entry for Memcached and click View Details.
Select the Dashboards tab to see a static preview. If the dashboard is installed, then you can navigate to it by clicking View dashboard.

For more information about dashboards in Cloud Monitoring, see Dashboards and charts.

For more information about using the Integrations page, see Manage integrations.

Install alerting policies

Alerting policies instruct Cloud Monitoring to notify you when specified conditions occur. The Memcached integration includes one or more alerting policies for you to use. You can view and install these alerting policies from the Integrations page in Monitoring.

To view the descriptions of available alerting policies and install them, do the following:

In the Google Cloud console, select Monitoring or click the following button:
Go to Monitoring
In the navigation pane, select Integrations.
Locate the entry for Memcached and click View details.
Select the Alerts tab. This tab provides descriptions of available alerting policies and provides an interface for installing them.
Install alerting policies. Alerting policies need to know where to send notifications that the alert has been triggered, so they require information from you for installation. To install alerting policies, do the following:
1. From the list of available alerting policies, select those that you want to install.
2. In the Configure notifications section, select one or more notification channels. You have the option to disable the use of notification channels, but if you do, then your alerting policies fire silently. You can check their status in Monitoring, but you receive no notifications.
  
  For more information about notification channels, see Manage notification channels.
3. Click Create Policies.

For more information about alerting policies in Cloud Monitoring, see Introduction to alerting.

For more information about using the Integrations page, see Manage integrations.

What's next

For a walkthrough on how to use Ansible to install the Ops Agent, configure a third-party application, and install a sample dashboard, see the Install the Ops Agent to troubleshoot third-party applications video.