Prometheus

In our Private Managed Clusters, Prometheus will automatically scan all Deployments, DaemonSets, and StatefulSets for a scraping port.

If you want to use scraping, you need to add the following annotations, example:

apiVersion: apps/v1beta2
kind: DaemonSet
...
spec:
  template:
    annotations:
      prometheus.io/port: "7472"
      prometheus.io/scrape: "true"
...

Alerts

To attach alerts to your Dashboard panels, enter the panel’s edit mode and go to the alert tab. From there, you can configure the conditions for the alert to trigger.

Note

Currently is it only possible to create rules on graph panels.

More in-depth documentation can be found here: Grafana-alerts

Alert notification channel

An alert notification channel can be set up in the Alerting section of the Dashboard (Bell icon in side bar). Click on Notification channels -> Add channel.

Supported notifiers

  • DingDing
  • Discord
  • Google
  • Hipchat
  • Kafka
  • Line
  • Microsoft Teams
  • Opsgenie
  • Pagerduty
  • Prometheus Alertmanager
  • Pushover
  • Sensu
  • Sensu Go
  • Slack
  • Telegram
  • Threema
  • VictorOps
  • Webhook
  • Zenduty

More in-depth documentation can be found here: Grafana-notifications

All your Kubernetes cluster in one place

Each Kubernetes cluster attaches a unique identifier label to all its metrics.

To separate metrics data in a Dashboard, create an ad-hoc filter on the Dashboard.

  1. Go to your dashboard and click Dashboard Settings (Cogwheel, top bar - right side)
  2. Click on Variables -> New
  3. Fill out the fields name and type (Has to be ad hoc)
  4. Go back to the dashboard. A new selector will now appear at the top of the dashboard. Search for the label: cluster
  5. Select cluster ID in the select value box and you will only see data from the chosen cluster

Access to this Dashboard happens through the ASERGO Dashboard