Grafana Dashboards

ONZACK Grafana Dashboards for Kubernetes, OpenShift and other systems.

Kubernetes / OpenShift Base Monitoring

ONZACK worked with LGT Bank in Liechtenstein to create two Grafana dashboards for Kubernetes and OpenShift. LGT Bank and ONZACK have agreed to make the dashboards available to the Kubernetes and OpenShift community so that everyone can benefit from the dashboards. ONZACK will continue to maintain and develop the dashboards in the future.

Cluster Monitoring

Download ONZACK Cluster Monitoring Dashboard without recording rules
Download ONZACK Cluster Monitoring Dashboard with recording rules
Download Prometheus Recording Rules for ONZACK Cluster Monitoring Dashboard

Troubleshooting

When using our dashboard with kube-prometheus-stack installed with helm and the custom rules are installed as yaml files, set ruleSelectorNilUsesHelmValues: false in the values.yaml for prometheus to load them.
Make sure your nodes are labeled correctly:

kubectl label node <YOUR-WORKERNODE> node-role.kubernetes.io/worker=worker
kubectl label node <YOUR-CONTROLPLANENODE> node-role.kubernetes.io/control-plane=control-plane

Namespace Monitoring

Download ONZACK Namespace Monitoring Dashboard without recording rules
Download ONZACK Namespace Monitoring Dashboard with recording rules
Download Prometheus Recording Rules for ONZACK Namespace Monitoring Dashboard

Falco Monitoring

Falco, the cloud-native runtime security project, is the de facto Kubernetes threat detection engine. This dashboard gives a good overview of the events generated by Falco.

Prerequisites

Falco
Falcosidekick -> to ship the Falco events to Loki
Loki (Datasource)

Longhorn Monitoring

Longhorn is a distributed block storage system for Kubernetes. This dashboard has been built to serve as an example for monitoring the Longhorn storage system.

Prerequisites

Longhorn
Prometheus ServiceMonitor for Longhorn
Add Longhorns example PrometheusRules (Alerting Rules)

OPNsense & IDS/IPS Monitoring

Dashboards to monitor Firewall Rules & IDS/IPS potential Attacks.

Prerequisites

Loadbalancer to create virtual IP and to publish syslog ports (for example MetalLB)
Promtail or Grafana Agent to listen on these ports and ship the logs to Loki
Loki to index the logs
Grafana to visualize the logs (datasource Loki configured)
OPNsense syslog target configured

The Grafana Dashboard only works when your OPNsense IDS/IPS logs has a label job: syslog-ids and all other Firewall logs has a label job: syslog.

Promtail Helm chart example values:

config:
  lokiAddress: "http://loki-gateway/loki/api/v1/push"
  snippets:
    extraScrapeConfigs: |
      # Add an additional scrape config for syslog
      - job_name: syslog
        syslog:
          listen_address: 0.0.0.0:514
          idle_timeout: 60s
          label_structured_data: yes
          labels:
            job: "syslog"
        relabel_configs:
          - source_labels: ['__syslog_message_hostname']
            target_label: 'host'
      # Add an additional scrape config for OPNsense IDS alerts shipped over syslog
      - job_name: syslog-ids
        syslog:
          listen_address: 0.0.0.0:1514
          idle_timeout: 60s
          label_structured_data: yes
          labels:
            job: "syslog-ids"
        relabel_configs:
          - source_labels: ['__syslog_message_hostname']
            target_label: 'host'

extraPorts:
  # Add an additional port for syslog
  # serviceType "LoadBalancer" only works if you have deployed an Loadbalancer for example MetalLB
  syslog:
    name: tcp-syslog
    containerPort: 514
    protocol: TCP
    service:
      type: LoadBalancer
      #clusterIP: null
      port: 514
      #externalIPs: []
      #nodePort: 32682
      #annotations: {}
      #labels: {}
      #loadBalancerIP: null
      #loadBalancerSourceRanges: []
      #externalTrafficPolicy: null
  # Add an additional port for OPNsense IDS alerts shipped over syslog
  # serviceType "LoadBalancer" only works if you have deployed an Loadbalancer for example MetalLB
  syslog-ids:
    name: tcp-syslog-ids
    containerPort: 1514
    protocol: TCP
    service:
      type: LoadBalancer
      #clusterIP: null
      port: 1514
      #externalIPs: []
      #nodePort: 32682
      #annotations: {}
      #labels: {}
      #loadBalancerIP: null
      #loadBalancerSourceRanges: []
      #externalTrafficPolicy: null

Velero Monitoring

Velero is an open source tool to safely backup and restore, perform disaster recovery, and migrate Kubernetes cluster resources and persistent volumes. This dashboard gives a good overview of the events and performance of Velero.

Prerequisites

Velero

Systemd Monitoring

Monitor state of systemd services running on the node.

Prerequisites

Node Exporter with Systemd collector enabled (Note: in order to collect metrics you need to mount /var/run/dbus/system_bus_socket into node-exporter and allow read access in Apparmor, if enabled)

Licence

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

onzack / grafana-dashboards Goto Github PK