Supported telemetry types
The integration supports these telemetry types:Prerequisites
The integration has the following prerequisites:- A Memcached server that listens on a TCP port the CXDOT Collector can reach. Unix domain sockets aren’t supported.
- A Memcached server that accepts unauthenticated connections. The integration uses
the plain-text
statscommand and doesn’t support servers that require SASL authentication.
Configure
The Memcached integration is enabled by default. You can configure targets either by annotating pods in your Kubernetes cluster or by listing static endpoints in your Helm values. To configure the integration, follow these steps:-
To collect from Memcached pods in Kubernetes, add a CXDOT integration annotation to
the pod template. The annotation key must end with the container name. For example,
add the following annotation to your Memcached workload:
The Collector replaces
${target.host}with the pod IP address and${target.port.memcached}with the container port namedmemcached. The Collector also discovers Memcached pods that carry theapp.kubernetes.io/name: memcachedlabel and listen on port11211. A CXDOT integration annotation takes precedence over the label for its container. To stop collecting from a container, setmemcached: {enabled: false}in the annotation. For more information, see autodiscovery. -
Optional: To collect from Memcached servers outside your Kubernetes cluster,
configure static targets. For example, add the following to the
values.yamlfor your CXDOT Collector Helm chart:When you configure static targets, this integration instance collects from exactly those targets instead of discovered targets. -
Optional: Configure a second integration instance to collect from both discovered
pods and static targets. For example, add the following to the
values.yamlfor your CXDOT Collector Helm chart:Thememcached/externalkey defines a named instance for the static targets. The barememcachedkey continues to discover pods. -
Optional: Disable the integration when you don’t want the CXDOT Collector to collect
Memcached metrics. For example, add the following to the
values.yamlfor your CXDOT Collector Helm chart:
Validate
To validate the integration, follow these steps:-
In Live Telemetry Analyzer, filter for
__name__=cxdot.integration.target.healthandcxdot.integration.name=memcached. Confirm that each expected target reports1. A value of1means that thestatscommand succeeded. A value of0means that it failed. Use theserver.addressandserver.portattributes to identify each target. -
In Metrics Explorer, run the following query:
Confirm that the query returns one time series per target.
Configuration reference
Configure one Memcached integration instance with the following settings. In Helm values, place these settings undercollection.cxdot.integrations.memcached. In a Collector configuration
file, place them under cxdot.integrations.memcached.
Optional settings
-
enabledType:boolean. Optional. Default:true. Whether to run the Memcached integration. If true, the Collector collects Memcached metrics. If false, the Collector doesn’t run this integration. -
endpointsType:array of object. Optional. Default:[]. Memcached targets. Each entry’sendpointishost:port, for example,memcached.default.svc:11211. When this list isn’t empty, the integration collects from exactly these targets instead of discovered targets. The integration uses the plain-textstatscommand and doesn’t support servers that require authentication. -
endpoints[].endpointType:string. Required. Memcached target inhost:portformat. -
collection_intervalType:duration. Optional. Default:10s. Time between metric collections from each Memcached target. -
timeoutType:duration. Optional. Default:10s. Maximum time to wait for each Memcached metric collection.