Grafana Chaos Annotation
Grafana chaos annotation action annotates the grafana dashboard to highlight the chaos duration.
Infrastructure type
Kubernetes
Use cases
Grafana Chaos Annotation action helps you:
Visualize chaos injection periods directly on Grafana dashboards
Correlate chaos events with metrics, logs, and alerts
Track experiment timeline alongside application performance metrics
Improve incident analysis and post-chaos debugging
Create visual markers for chaos engineering activities
Overview
This action creates annotations on Grafana dashboards to mark the start and duration of chaos experiments. Annotations appear as vertical lines or regions on your dashboards, making it easy to correlate chaos events with system behavior and performance metrics.
Action type
Custom Script Action
Prerequisites
Grafana instance with API access enabled
Grafana username and password with annotation write permissions
Dashboard UID where annotations will be created
Kubernetes cluster with chaos infrastructure installed
Network connectivity from chaos infrastructure to Grafana API endpoint
Action properties
Script details
The action executes a custom script that:
Authenticates with Grafana API using username and password
Creates an annotation based on the specified mode (SOT/EOT/Continuous)
Tags the annotation for easy filtering and identification
Command and Arguments
Command: actions
Arguments:
-name grafana-chaos-annotation-uid <dashboard-uid>
Environment variables
GRAFANA_URL
URL of the Grafana instance
Yes
-
https://grafana.example.com
GRAFANA_USERNAME
Username for Grafana authentication
Yes
-
admin
GRAFANA_PASSWORD
Password for Grafana authentication
Yes
-
your-password
DASHBOARD_UID
Dashboard UID of the Grafana instance
Yes
-
abc123def456
MODE
Mode of operation for the annotation
Yes
-
SOT, EOT, Continuous
ADDITIONAL_TAGS
Additional tags for the annotation
No
-
chaos,k8s,production
Run properties
timeout
Maximum time to wait for the action to complete (e.g., 30s, 1m, 5m)
String
30s
interval
Time between action executions (e.g., 1s, 5s, 10s)
String
1s
iterations
Number of times the action should execute
Integer
1
maxRetries
Number of retry attempts before marking the action as failed
Integer
1
initialDelay
Initial delay before starting the action (e.g., 0s, 10s, 30s)
String
-
Parameters
The following YAML snippet illustrates the use of these tunables:
Next Steps
Last updated
Was this helpful?