# Grafana Plugin CI

Grafana Plugin CI is a collection of reusable GitHub Actions workflows and actions for building, testing, and deploying Grafana plugins. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5361/grafana-plugin-ci

## Description

Grafana Plugin CI is a collection of reusable GitHub Actions workflows and actions for building, testing, and deploying Grafana plugins. It standardizes the CI/CD pipeline with consistent frontend and backend builds, automated unit and end-to-end tests, and deployment steps, so plugin developers can integrate it into their own repositories for reliable, repeatable releases. The workflows are maintained by Grafana Labs for its internal plugin teams; external developers may find the plugin-actions repository a better fit.

## Platform availability

Available on 0 of 10 platforms.

## Health score

70/100 (Good), based on 5 of 5 factors.
- Maintained: 100 (last commit 15 days ago)
- Popular: 21 (10 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 95 (512 MB minimum RAM, runs on ARM)
- Security check: 100 (no serious findings, CI, tests)

## Links

- Docker Hub: https://hub.docker.com/r/grafana/grafana-plugin-ci
- GitHub: https://github.com/grafana/plugin-ci-workflows

## Common questions

### Does provenance checking work when Grafana plugin CI workflows run on self-hosted runners?

No, the provided issue states that provenance doesn't work with self-hosted runners. It was moved from Triage to Ideation by the Grafana Catalog Team.

### Is there a request to have Canvas use internal plugin CI workflows instead of community ones?

Yes, an issue in the Grafana repository asks the Canvas project to use internal plugin CI workflows instead of community ones.

### Where can plugin developers find discussions about signing and publishing Grafana plugins?

The Grafana Labs Community forum has a plugin development category that includes signing and publishing plugin discussions. It also includes areas for announcements and showcasing new plugins.

### What should a self-hosted Grafana user do if plugin testing causes high memory or CPU usage?

The documentation says to configure profiling and tracing to troubleshoot backend performance problems such as high memory or CPU usage.

## Alternatives

- Beszel: A lightweight server monitoring hub with historical data, docker stats, and alerts.
- Datadog: Datadog Agent is an on-host monitoring agent that collects metrics, logs, and traces from hosts, containers, and Kubernetes clusters and se…
- DeepFlow: Unify your cloud-native monitoring with zero-code eBPF, advanced profiling, and 10x storage efficiency.
- Kibana: Kibana is the data visualization layer for querying, analyzing, and managing data stored in Elasticsearch.
- Metabase: Metabase is a simple and powerful analytics tool which lets anyone learn and make decisions from their company’s data.
- Netdata: Netdata is a real-time performance and health monitoring solution that collects per-second metrics from your servers, containers, networks,…
- OpenSearch: OpenSearch is an open-source search and observability suite for self-hosters who need scalable indexing, analysis, and visualization of log…
- SigNoz: SigNoz is a self-hostable open-source observability platform that unifies logs, metrics, traces, alerts, and dashboards using OpenTelemetry…
- Splunk: Splunk is a self-hosted platform for collecting, indexing, searching, and analyzing log and security data, helping homelabbers and operatio…
- Tableau: Tableau helps the world’s largest organizations unleash the power of their most valuable assets: their data and their people.
- VictoriaLogs: VictoriaLogs is a high-performance, lightweight, schema-free database for logs.
- apache-superset: Apache Superset is a modern data exploration and visualization platform.

---
Source: Our Local Host (https://ourlocalhost.com/app/5361/grafana-plugin-ci), the self-hosted and open-source app directory.
