When using Redis, you need to monitor its running status to know whether it runs normally and troubleshoot its faults. TMP provides an exporter to monitor Redis and offers an out-of-the-box Grafana monitoring dashboard for it. This document describes how to use TMP to monitor Redis.
Note:
For easier export installation and management, we recommend you use TKE for unified management.
Prerequisites
You have created a TKE cluster in the region and VPC of your TMP instance and created a namespace for the cluster.
You have located and integrated the target TKE cluster in the Integrate with TKE section of the target TMP instance in the TMP console. For more information, please see Agent Management.
1. On the left sidebar, select Workload > Deployment to enter the Deployment page.
2. In the top-right corner of the page, click Create via YAML to create a YAML configuration as detailed below:
You can use Kubernetes Secrets to manage and encrypt passwords. When starting the Redis exporter, you can directly use the Secret key but need to adjust the corresponding password. Below is a sample YAML configuration:
On the Deployment management page, click Create and select the target namespace to deploy the service. You can create in the console. Here, YAML is used to deploy the exporter. Below is a sample YAML configuration:
Note:
For more information on the detailed exporter parameters, please see redis_exporter.
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
k8s-app: redis-exporter # Rename the exporter based on the business needs. We recommend you add the Redis instance information
name: redis-exporter # Rename the exporter based on the business needs. We recommend you add the Redis instance information
namespace: redis-test
spec:
replicas:1
selector:
matchLabels:
k8s-app: redis-exporter # Rename the exporter based on the business needs. We recommend you add the Redis instance information
template:
metadata:
labels:
k8s-app: redis-exporter # Rename the exporter based on the business needs. We recommend you add the Redis instance information
spec:
containers:
-env:
-name: REDIS_ADDR
value: ip:port # `ip:port` of the corresponding Redis instance
name: metric-port # This name is required during scrape task configuration
securityContext:
privileged:false
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
dnsPolicy: ClusterFirst
imagePullSecrets:
-name: qcloudregistrykey
restartPolicy: Always
schedulerName: default-scheduler
securityContext:{}
terminationGracePeriodSeconds:30
Verifying
1. Click the newly created Deployment on the Deployment page to enter the Deployment management page.
2. Click the Log tab, and you can see that the exporter is successfully started and its address is exposed as shown below:
3. Click the Pod Management tab to enter the Pod page.
4. In the Operations column on the right, click Remote Login to log in to the Pod. Run the following curl command with the address exposed by the exporter in the command line window, and you can get the corresponding Redis metrics normally. If no corresponding data is returned, please check whether REDIS_ADDR and REDIS_PASSWORD are correct as shown below:
curl localhost:9121/metrics
The command execution result is as shown below:
Adding scrape task
1. Log in to the TMP console and select the target TMP instance to enter the management page.
2. Click a cluster ID in the TKE cluster list to enter the Integrate with TKE page.
3. In Scrape Configuration, add Pod Monitor to define a Prometheus scrape task. Below is a sample YAML configuration:
apiVersion: monitoring.coreos.com/v1
kind: PodMonitor
metadata:
name: redis-exporter # Enter a unique name
namespace: cm-prometheus # The namespace is fixed. Do not change it
spec:
podMetricsEndpoints:
-interval: 30s
port: metric-port # Enter the name of the corresponding port of the Prometheus exporter in the Pod YAML configuration file
path: /metrics # Enter the value of the corresponding path of the Prometheus exporter. If it is not specified, it will be `/metrics` by default
relabelings:
-action: replace
sourceLabels:
- instance
regex: (.*)
targetLabel: instance
replacement:'crs-xxxxxx'# Change it to the corresponding Redis instance ID
-action: replace
sourceLabels:
- instance
regex: (.*)
targetLabel: ip
replacement:'1.x.x.x'# Change it to the corresponding Redis instance IP
namespaceSelector:# Select the namespace where the Pod to be monitored resides
matchNames:
- redis-test
selector:# Enter the label value of the Pod to be monitored to locate the target Pod
matchLabels:
k8s-app: redis-exporter
Note:
As the exporter and Redis are deployed on different servers, we recommend you use the Prometheus relabeling mechanism to add the Redis instance information to the monitoring metrics so as to locate problems more easily.
Viewing monitoring information
1. Log in to the TMP console and select the target TMP instance to enter the management page.
2. Click Integration Center to enter the Integration Center page. Find Redis monitoring, install the corresponding Grafana dashboard, and then you can enable the Redis monitoring dashboard to view instance monitoring data as shown below:
Integrating with alert feature
1. Log in to the TMP console and select the target TMP instance to enter the management page.
2. Click Alerting Rule and add the corresponding alerting rules. For more information, please see Creating Alerting Rule.
Yes
No
Was this page helpful?