Download PDF
Download page GCP Memorystore for Memcached.
GCP Memorystore for Memcached
Google Cloud Platform (GCP) Memorystore for Memcached is a highly scalable, fully managed Memcached service for Google Cloud.
Cisco Cloud Observability supports monitoring the following Memorystore for Memcached entities:
- Instance: Represents one instance of a Memcached cluster. An instance can be comprised of a single node or a collection of nodes.
- Node: The fundamental unit of a Memcached instance. All nodes in an instance must have the same memory per node and the same number of vCPUs.
You must configure cloud connections to monitor this entity. See Configure Google Cloud Platform Connection.
Cisco Cloud Observability displays GCP entities on the Observe page. Metrics are displayed for specific entity instances in the list and detail views.
This document contains references to third-party documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.
Detail View
To display the detail view of a Memorystore for Memcached instance:
- Navigate to the Observe page.
- Under Database & Storage, click GCP Memcached Instances.
The list view now displays. - From the list, click an entity Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the instance you selected.
- Navigate to the Observe page.
- Under Database & Storage, click GCP Memcached Instances.
- From the Relationships panel on the left, click GCP Memcached Nodes.
The list view now displays. - From the list, click an entity Name to display the detail view.
The detail view displays metrics, key performance indicators, and properties (attributes) related to the instance you selected.
Metrics and Key Performance Indicators
Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for GCP Memorystore for Memcached instances and nodes. See Google Cloud metrics.
| Display Name | Source Metric | Description |
|---|---|---|
| Active Connections (Count) |
| The connections active in this Memcached node. |
| Cache Memory (By) |
| The bytes allotted for the Memcached cache in this node, grouped by whether that memory is used or not. |
| Total CPU Time (s) |
| The CPU usage time by Memcached process, grouped by user and kernel mode. |
| CPU Utilization (%) |
| The CPU usage percentage by Memcached node. |
| Evictions (Count) |
| The count of items evicted by this Memcached node. |
| Hit Rate (%) |
| The hit ratio, expressed as a percentage of the total cache requests excluding set operations. |
| Items (Count) |
| The count of items stored in this Memcached node. |
| Memory Utilization (%) |
| The utilization of system memory by Memcached node. |
| Operations (Count) |
| The count of Memcached operations. |
| Network I/O (By) |
| The bytes sent/received by this Memcached node. |
| Uptime (s) |
| The time in seconds the node has been running. |
Properties (Attributes)
Cisco Cloud Observability displays the following properties for GCP Memorystore for Memcached.
| Display Name | Source Property Name | Description |
|---|---|---|
| ID | name | The unique ID of the resource in this scope, including project and location, using the format projects/{projectId}/locations/{locationId}/clusters/{clusterId}. |
| Name | - | The name of the resource, parsed from the ID. |
| Project ID | - | The ID of the GCP project. |
| Region | - | The location of the cluster. |
| Zones | zones | A comma-separated list of zones in which Memcached nodes should be provisioned. |
| Major Version | memcachedVersion | The major version of Memcached software. If not provided, the latest supported version will be used. The minor version will be automatically determined by our system based on the latest supported minor version. |
| Full Version | memcacheFullVersion | Output only. The full version of the Memcached server running on this instance. The system automatically determines the full Memcached version for an instance based on the input MemcacheVersion. An example of the full version format is memcached-1.5.16. |
| State | state | Output only. The state of this Memcached instance. |
Create Time |
| Output only. The time the instance was created. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: "2014-10-02T15:01:23Z" and "2014-10-02T15:01:23.045123456Z". |
| Update Time |
| Output only. The time the instance was updated. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: "2014-10-02T15:01:23Z" and "2014-10-02T15:01:23.045123456Z". |
| Endpoint |
| Output only. Endpoint for the Discovery API. |
| Display Name | Source Property Name | Description |
|---|---|---|
| ID | name | The ID of the node. Internal and includes the instance ID as a prefix. |
| Name | - | The name of the resource, parsed from the ID. |
| Project ID | - | The ID of the GCP project. |
| Region | - | The location of the node. |
| Host | host | Output only. The host name or IP address of the Memcached node used by the clients to connect to the Memcached server on this node. |
| Port | port | Output only. The port number of the Memcached server on this node. |
Retention and Purge Time-To-Live (TTL)
For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days).
Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.