Aller au contenu

CloudeyeExporterMetricsMissingFE#

This alert is triggered when cloudeye-exporter metrics are missing 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#

  • Check that servicemonitor is present

    kubectl get servicemonitor -n cloudeye-exporter cloudeye-exporter-metrics
    
  • Check if the exporter is healthy

    export NAMESPACE=cloudeye-exporter
    kubectl get pods -l app.kubernetes.io/instance=cloudeye-exporter -n $NAMESPACE
    kubectl logs -l app.kubernetes.io/instance=cloudeye-exporter -n $NAMESPACE
    
  • Check that cloudeye-exporter metrics (ex: go_info{job="cloudeye-exporter"}) are available on the related Grafana (Caascad and Ngot).

For Caascad zone, choose either the Thanos datasource if the problem concerns the cloud zone or Thanos-client if it is about a client zone (the only client zones where cloudeye-exporter is deployed is corp).

For NGOT zone, choose the Thanos datasource.