Aller au contenu

CloudeyeExporterResourcesMetricsMissingFE#

This alert is triggered when no metrics from cloudeye-exporter named flexibleengine_XXX are received for more than 10 minutes.

Warning

There are three alerts.

  • CloudeyeExporterMetricsMissingFE: Fires when cloudeye-exporter is not running correctly. Fires only for Caascad clients and for mon3/mon4 on Ngot.
  • CloudeyeExporterClientMetricsMissingFE: Fires when cloudeye-exporter is not running correctly. Fires only for Ngot clients.
  • CloudeyeExporterResourcesMetricsMissingFE: Fires when cloudeye-exporter does not collect any metrics. Fires only on Ngot (both client and mon3/mon4).

When CloudeyeExporterResourcesMetricsMissingFE and another alerts are both firing, first investigate on the other one.

Cloudeye-exporter doc here.

Troubleshooting hints#

Tip

Below, <monitoring_namespace> is built with the namespace label from the Karma alert.

  • Ensure that the ServiceMonitor for cloudeye-exporter is correctly configured and present in the namespace:

    kubectl get servicemonitor -n $NAMESPACE cloudeye-exporter

  • Check if the exporter is healthy:

    kubectl get pods -l app.kubernetes.io/instance=cloudeye-exporter -n $NAMESPACE
kubectl logs -l app.kubernetes.io/instance=cloudeye-exporter -n $NAMESPACE

  • Verify that the metrics named flexibleengine_XXX are available on the related Grafana (choose the Thanos datasource).

  • Check in Prometheus (central) the targets (do a port forward, more information here). Check if the target exists. Check its state. If the target is unhealthy, Prometheus may provide an explanation.