Kubeshark Dashboard v3.10
This dashboard provides a holistic view of Kubeshark resource consumption, in addition to custom metrics that offer insights into what Kubeshark is doing internally
Metrics
Kubeshark provides metrics from worker components.
It can be useful for monitoring and debugging purpose.
Configuration
By default, Kubeshark uses port 49100 to expose metrics via service kubeshark-worker-metrics.
In case you use [kube-prometheus-stack] (https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack) community Helm chart, additional scrape configuration for Kubeshark worker metrics endpoint can be configured with values:
prometheus:
enabled: true
prometheusSpec:
additionalScrapeConfigs: |
- job_name: 'kubeshark-worker-metrics'
kubernetes_sd_configs:
- role: endpoints
relabel_configs:
- source_labels: [__meta_kubernetes_pod_name]
target_label: pod
- source_labels: [__meta_kubernetes_pod_node_name]
target_label: node
- source_labels: [__meta_kubernetes_endpoint_port_name]
action: keep
regex: ^metrics$
- source_labels: [__address__, __meta_kubernetes_endpoint_port_number]
action: replace
regex: ([^:]+)(?::\d+)?
replacement: $1:49100
target_label: __address__
- action: labelmap
regex: __meta_kubernetes_service_label_(.+)Available metrics
Summary
This dashboard provides a holistic view of Kubeshark resource consumption, in addition to custom metrics that offer insights into what Kubeshark is doing internally
Data source config
Collector config:
Upload an updated version of an exported dashboard.json file from Grafana
| Revision | Description | Created | |
|---|---|---|---|
| Download |