Day-two work on a running Grafana: monitoring Grafana itself, caching and database tuning, backups, admin recovery, scaling for users and keeping outbound traffic under control.
Watching the health of the Grafana server: scraping /metrics and plugin metrics, protecting the endpoint, tracing HTTP API calls with OTLP, and the dashboards and alerts that catch slow queries and failing data sources.
When to move Grafana's cache from the database to Redis or Memcached, what the remote cache holds and what stays in the database, and sizing the cache for a multi-instance deployment.
Tuning the Grafana database connection pool for many users and alert rules: max open and idle connections, connection lifetime against MySQL timeouts, and spotting database contention in Grafana's own metrics.
Backing up a self-hosted Grafana so it can be rebuilt: database dumps, configuration and plugin folders, provisioning files in Git, restore order, and testing that a restored instance actually works.
Getting back into Grafana when the admin password is lost: grafana cli admin reset-admin-password, finding the right user ID, pointing the CLI at an external database, and preventing lockouts with SSO admin mapping.
Estimating CPU, memory and database capacity for Grafana: the small deployment baseline, what grows load (concurrent viewers, panel refresh rates, alert rules), and when to add instances behind a load balancer.
Keeping Grafana Live streaming panels working: WebSocket upgrade headers on /api/live/, proxy connection limits, and the documented limitations of Grafana Live in highly available setups.
Stopping a self-hosted Grafana from calling home: anonymous usage reporting, external snapshot publishing, plugin catalog and update checks, and what changes for regulated or air-gapped networks.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.