Skip to content
You are viewing the documentation for Solo Enterprise for Istio, formerly known as Gloo Mesh (OSS APIs).

For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Alerts

Page as Markdown

Review alerts for Solo Enterprise for Istio components that are automatically configured for you in Prometheus.

About

To monitor the Solo Enterprise for Istio components more easily, Solo Enterprise for Istio automatically sets up alerts for certain metrics. These metrics include:

  • Connected agents: Monitors the connection between the management server and agents in connected clusters.
  • Redis errors: Lists connection failures between the management server and the Redis database where all Solo Enterprise for Istio configuration is stored.

To view the alerts that Solo Enterprise for Istio automatically sets up and any alerts that you configure in your Solo Enterprise for Istio 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

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 ${context1} \
    -o=jsonpath='{.data.alerting_rules\.yml}' | \
    base64 -d

Agent alerts

Solo Enterprise for Istio automatically monitors the relay connection between the management server and agents, and notifies you if issues are found.

GlooPlatformAgentsAreDisconnected

This alert is used to notify you when an agent in a registered workload cluster is not connected to the management server. By default, you get a warning alert as soon as one agent 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).

CharacteristicValue
TypeCounter
Expressioncount by(cluster) (sum by(cluster) (relay_push_clients_warmed == 0)) > 0
Duration5 Minutes
SeverityWarning
Recommended troubleshooting guideRelay connection
Agent

Redis alerts

Solo Enterprise for Istio sets up alerts to monitor the read and write operations between the management server and Redis.

GlooPlatformRedisErrors

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

CharacteristicValue
TypeCounter
Expressionincrease(gloo_mesh_redis_sync_err_total[5m]) > 0
SeverityWarning
Recommended troubleshooting guideLink