The fleet monitoring feature in ACK One uses metrics from Managed Service for Prometheus to provide a monitoring dashboard for your Fleet. You can create custom alert rules to monitor key metrics in real time.
Prerequisites
-
You have enabled fleet monitoring. For more information, see Enable fleet monitoring.
-
You have created a notification object. For more information, see Notification objects.
NoteIf you use a DingTalk chatbot as a notification object, you must add custom keywords for alerts in the chatbot's security settings.
Configure alerts for Argo CD in ACK One
-
Log on to the ACK One console. In the navigation pane on the left, choose .
-
On the Fleet Monitoring page, click Alert Settings in the upper-right corner to open the Prometheus alert rules page.
-
Click Create Prometheus Alert Rule, configure the parameters as described in the following table, and then click Complete. For more information, see Create a Prometheus alert rule template.
Parameter
Description
Example
Alert Name
The name of the custom alert rule.
ACK One Argo CD Pod memory alert
Check type
You can select Static Threshold or Custom PromQL.
Select Static Threshold.
Prometheus Instance:
Enter the name of your ACK One Fleet.
text-XXXX
Alert Contact Group
The Kubernetes group to monitor in your environment.
Kubernetes workload
Alert Metric:
Select a metric based on your requirements. We recommend that you focus on Container Memory Usage and container CPU utilization.
Container Memory Usage
Alert Condition:
Set the conditions for triggering an alert event based on the preset content of the alert metric.
The alert condition is met when the container CPU utilization is
greater than80%.Filter Condition
Based on the alert metric, set the scope for the alert rule. An alert event is triggered for any resource that meets both the filter conditions and the alert condition.
The available filter conditions are:
-
Traverse: The alerting rule applies to all resources in the current Prometheus instance. By default, the filter condition is set to Traversal.
-
Equal To: After selecting this condition, enter a specific resource name. The alert rule will apply only to that resource. You cannot enter multiple resources.
-
Is not equal: After selecting this condition, enter a specific resource name. The alert rule will apply to all resources except that one. You cannot enter multiple resources.
-
Match Regular Expression: After selecting this condition, enter a regular expression to match resource names. The alert rule will apply to all resources that match the expression.
-
Do Not Match Regular Expression: After selecting this condition, enter a regular expression to match resource names. The alert rule will filter out all resources that match the expression.
namespace equals argocd, Pod: Traverse, container: Traverse.
Duration
-
Trigger an alert event as soon as the alert condition is met: An alert event is triggered if any data point meets the threshold.
-
Trigger an alert event only when the alert condition persists for N minutes: An alert event is triggered only if the threshold is met for N minutes or more.
An alert is triggered if the alert condition persists for 1 minute.
Alert Level
The severity of the alert. The default severity is Default. The severity levels, from lowest to highest, are Default, P4, P3, P2, and P1.
P1
Alert Message
The alert information that users receive. You can use Go template syntax to customize alert parameter variables in the alert content.
Namespace: {{$labels.namespace}} / Pod: {{$labels.pod_name}} / Container: {{$labels.container}} CPU utilization {{$labels.metrics_params_opt_label_value}} {{$labels.metrics_params_value}}%, current value {{ printf "%.2f" $value }}%
Alert Notification
You can select Simple Mode or Standard Mode.
Select Simple Mode.
Notification Contacts
The destination for alert notifications.
DingTalk alert
Notification Period
The time range for sending notifications.
23:00 to 01:00
Whether to Resend Notifications
The interval at which to resend notifications for an unresolved alert.
Resend notifications every 10 minutes.
-
-
After completing the configuration, trigger the alert condition to verify that you receive the alert notification.
NoteYou can view the alert history in the Prometheus console. For more information, see View alert history.