Adopt PromQL metric views → Elastic (workshop)
When to use
Metrics adoption practice for existing Elastic customers: Grafana/PromQL exports in assets/grafana/ (20 dashboards)
and assets/grafana/alerts/ (unified alert rules for --fetch-alerts)
→ observability-migration-platform grafana-migrate
→ build/mig-grafana/ + Kibana upload (--native-promql), then tools/publish_grafana_alert_drafts_kibana.py for Rules.
Telemetry: OpenTelemetry SDK → Grafana Alloy → Elastic mOTLP. Restart: ./scripts/start_workshop_otel.sh.
Run (Instruqt)
bash /root/workshop/scripts/migrate_grafana_dashboards_to_serverless.sh
Waits for OTLP (or starts start_workshop_otel.sh), runs grafana-migrate with --upload --ensure-data-views --fetch-alerts, then publishes rules. Output: build/mig-grafana/dashboards/yaml/ (or yaml/), dashboards/migration_report.json, alerts/alert_comparison_results.json (legacy flat paths still work).
Set WORKSHOP_MIG_ES_VALIDATE=1 to add live ES|QL validation before upload.
Optional — laptop + Cursor
- Clone workshop repo;
./scripts/install_workshop_mig_to_kbn.sh - On VM:
grep -E '^export (KIBANA_URL|ES_URL|ES_API_KEY)=' ~/.bashrc— paste into laptop terminal - Run the same migrate script from repo root, or invoke
grafana-migratedirectly (seescripts/migrate_grafana_dashboards_to_serverless.sh)
Safety
- Never commit API keys.
- Validate panels against real metric names and labels in your Serverless project.