Use ARMS Prometheus Monitoring to monitor Redis databases
Last Updated: Feb 08, 2021
ARMS Prometheus Monitoring allows you to monitor Redis databases by capturing data
from the databases and presenting the captured data on the ARMS Prometheus Grafana
dashboard.
In the left-side navigation pane, click Clusters. On the Clusters page, click Applications in the Actions column corresponding to the cluster.
On the Workloads page, click the Deployments tab. On the Deployments tab, click Create from Template.
On the Deployments tab, select Custom from the Sample Template drop-down list. Enter the following text in the Template text editor and click Create to deploy the redis-exporter application to the ACK cluster.
Note Replace values of <Address> and <Password> with the corresponding values of the Redis database. You can also use the following
sample values provided by ARMS to experience the service:
In the left-side navigation pane, click Prometheus Monitoring.
In the upper-left corner of the Prometheus Monitoring page, select the region where your ACK cluster is deployed. Find the cluster and
click Settings in the Actions column.
On the Settings page, click the Service Discovery tab. On the Service Discovery tab, click Add ServiceMonitor. In the Add ServiceMonitor dialog box, enter the following content and click OK:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
# Enter a unique name.
name: redis-exporter
# Enter the desired namespace.
namespace: default
spec:
endpoints:
- interval: 30s
# The Redis Grafana template ID is 763.
# Enter the value of the Name field for Port of Prometheus Exporter in the service.yaml file.
port: redis-exporter
# Enter the value of the Path field for Prometheus Exporter.
path: /metrics
namespaceSelector:
any: true
# Demo namespace:
matchLabels:
# Enter the value of the Label field in the service.yaml file to find the service.yaml file.
app: redis-exporter
Step 3: Present data of the Redis database on the Grafana dashboard
Import the Grafana dashboard template and specify the ACK cluster where the Prometheus
data source is located.
In the left-side navigation pane, click Prometheus Monitoring.
In the top navigation bar, select a region. Then, click the name of the required Kubernetes
cluster.
In the left-side navigation pane, choose Alarm configuration beta. Then, click Create Alert in the upper-right corner.
In the Create Alert dialog box, configure the following parameters, and then click OK.
Note The Time parameter is not supported.
Enter a name in the Rule Name field. Example: alerts for inbound traffic.
Enter an expression that uses a PromQL statement. Example: (sum(rate(kube_state_metrics_list_total{job="kube-state-metrics",result="error"}[5m]))
/ sum(rate(kube_state_metrics_list_total{job="kube-state-metrics"}[5m]))) > 0.01.
Notice An error may be reported if a PromQL statement contains a dollar sign ($). You must remove the equal sign (=) and the parameters on both sides of the equal sign (=) from the statement that contains the dollar sign ($). For example, change sum (rate (container_network_receive_bytes_total{instance=~"^$HostIp.*"}[1m])) to sum (rate (container_network_receive_bytes_total[1m])).
In the Labels section, click Create Tag to specify alert tags. The specified tags can be used as options for a dispatch rule.
In the Annotations section, specify a template for alert messages. Click Create Annotation. Set Key to message and Value to {{variable name}} alert message. The specified annotation is in the format of message:{{variable name}} alert notification. Example: message:{{$labels.pod_name}} restart.
You can customize a variable name or select an existing tag as the variable name. Existing tags:
The tags that are carried in the metrics of an alert rule expression.
The tags that are created when you create an alert rule. For more information, see
Create an alert.
The default tags provided by ARMS. The following table describes the default tags.
Tag
Description
alertname
The name of the alert. The format is <Alert name>_<Cluster name>.
_aliyun_arms_alert_level
The level of the alert.
_aliyun_arms_alert_type
The type of the alert.
_aliyun_arms_alert_rule_id
The ID of the alert rule.
_aliyun_arms_region_id
The ID of the region.
_aliyun_arms_userid
The ID of the user.
_aliyun_arms_involvedObject_type
The subtype of the associated object, for example, ManagedKubernetes or ServerlessKubernetes.
_aliyun_arms_involvedObject_kind
The type of the associated object, for example, app or cluster.
_aliyun_arms_involvedObject_id
The ID of the associated object.
_aliyun_arms_involvedObject_name
The name of the associated object.
What to do next
After the ARMS Prometheus Grafana Redis dashboard is configured, you can view metrics
of Prometheus Monitoring and customize the dashboard. For more information, see the
following topics.