Alerts

To monitor the Gloo Mesh Core components more easily, Gloo automatically sets up alerts for certain metrics. These metrics include:

• Latency: The time it takes to translate or reconcile Gloo resources in your environment.
• Gloo agents: Monitors the connection between the Gloo management server and workload clusters.
• Translation errors: Reports the Gloo resources that cannot be correctly translated into Istio resources.
• Redis errors: Lists connection failures between the Gloo management server and the Redis database where all of the Gloo configuration is stored.

To view the alerts that Gloo automatically sets up and any alerts that you configure in your Gloo Mesh Core environment:

• Check the /alerts page of the Prometheus UI to manually review alerts.
• Deploy an instance of Prometheus Alertmanager to set up alert notifications.

View default alerts link

The Prometheus server alert configuration is stored in the gloo-prometheus-server secret in the gloo-mesh namespace. You can extract the alert configmap from that secret by using the following command:

  kubectl get secret gloo-prometheus-server -n gloo-mesh --context $MGMT_CONTEXT \
    -o=jsonpath='{.data.alerting_rules\.yml}' | \
    base64 -d
  

Latency alerts link

Gloo Mesh Core sets up default alerts that monitor the time it takes for a Gloo resource to get translated or reconciled.

GlooPlatformTranslationLatencyIsHigh link

Use this alert to receive warnings when the Gloo management server takes longer than usual to translate Gloo resources in to the corresponding Istio resources. The alert is configured as a histogram and is set on the 99th percentile. Alerts are sent when the translation time is higher than 10 seconds for 99% of the time during a specific timeframe.

You can customize this alert and for example send critical alerts when you reach the 99th percentile, and warnings for lower percentiles, such as 70. Note that the percentile value depends on your environment. For example, if the cluster that runs your Gloo management server is shared, you might to want use a lower percentile so that you have enough time to reschedule workloads or add resources if translation times become critical. On the other hand, if your cluster is dedicated to the Gloo management plane only and comes with additional compute resources, you can use higher percentile values for your critical alerts.

Review the default configuration of the alert. You can customize values, such as the severity, the overall timeframe that the threshold must meet before an alert is sent (duration), or the interval in which data is collected for the histogram (bucket distribution).

GlooPlatformReconcilerLatencyIsHigh link

The Gloo reconciler applies translated Gloo resources in your workload clusters so that the desired state in your Gloo environment can be reached. This alert notifies you when the time that the reconciler needs to apply the desired resources takes longer than 80 seconds. The alert is configured as a histogram and set on the 99th percentile.

You can customize this alert and for example send critical alerts when you reach the 99th percentile, and warnings for lower percentiles, such as 70. Note that the percentile value depends on your environment. For example, if the cluster that runs your Gloo management server is shared, you might want to use a lower percentile so that you have enough time to reschedule workloads or add resources if reconciliation times become critical. On the other hand, if your cluster is dedicated to the Gloo management plane only and comes with additional compute resources, you can use higher percentile values for your critical alerts.

Review the default configuration of the alert. You can customize values, such as the severity, the overall timeframe that the threshold must be met before an alert is sent (duration), or the interval in which data is collected for the histogram (bucket distribution).

Gloo agents alerts link

Gloo automatically monitors the relay connection between the Gloo management server and Gloo agents, and notifies you if issues are found.

GlooPlatformAgentsAreDisconnected link

This alert is used to notify you when a Gloo agent in a workload cluster is not connected to the Gloo management server. By default, you get a warning alert as soon as one cluster loses connectivity to the management server. However, depending on your cluster environment you might want to change this alert to critical.

Review the default configuration of the alert. You can customize values, such as the severity, or the overall timeframe that the threshold must be met before an alert is sent (duration).

Translation alerts link

Gloo automatically sets up alerts to monitor Gloo resources that cannot be translated correctly.

GlooPlatformTranslationWarnings link

Sometimes Gloo resource configurations include partial errors or refer to other unknown Gloo resources, such as a gateway or destination. When the Gloo management server translates the resource, the translation itself works, but referenced resources for example could not be found. The Gloo resource is then marked with a warning state. When a resource with a warning state is found during a 5 minute timeframe, the alert is triggered.

Review the default configuration of the alert. You can customize values, such as the expression or severity.

For more information about how to troubleshoot this error, see Istio and gateway lifecycle manager.

GlooPlatformTranslationErrors link

Translation errors can happen if the Gloo resource configuration is correct, but the Gloo management server has an issue with applying the resource or reconciling Gloo agents. If such an error occurs, the resource state changes to Failed. When a resource with a failed state is found during a 5 minute timeframe, the alert is triggered.

Review the default configuration of the alert. You can customize values, such as the expression or severity.

For more information about how to troubleshoot this error, see Istio and gateway lifecycle manager.

GlooPlatformClustersNotWarming link

For environments where safe mode is enabled, this alert is triggered when one or more Gloo management server replicas run in safe mode for more than 10 minutes. If you see this alert, make sure to check the workload clusters that triggered safe mode for connectivity issues. Safe mode might also be triggered, because of the Gloo management server or Redis being unavailable or unstable.

For more information about how to troubleshoot this error, see Management server or Agent .

Redis alerts link

Gloo sets up alerts to monitor the read and write operations between the Gloo management server and Redis.

GlooPlatformRedisErrors link

In the event that the Gloo management server cannot read from the Gloo Redis instance during a 5 minute timeframe, an alert is automatically triggered.