Prometheus

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

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

apiVersion: apps/v1beta2
kind: DaemonSet
metadata:
  annotations:
    prometheus.io/port: 7472
    prometheus.io/scrape: true
...

For a ServiceMonitor you need to create a ServiceMonitor map in the Prometheus namespace:

apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  labels:
    k8s-app: coredns
  name: coredns
  namespace: monitoring
spec:
  endpoints:
  - bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
    interval: 15s
    port: http-metrics
  jobLabel: k8s-app
  namespaceSelector:
    matchNames:
    - kube-system
  selector:
    matchLabels:
      component: metrics
      k8s-app: coredns

Dashboard

When you login first time are you asked to change the password.

Default credentials is admin:admin

Note

The dashboard is only exposed through your ASERGO Dashboard. Only members of your organization can gain access.

Alerts

You can attach alert rules to your dashboard panels. To attach an alerting to a panel simple enter edit mode of the panel and to go the alert tab. Here is it possible to configure its conditions for an alert 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
  • Email
  • 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 an 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