Installer grafana avec Homebrew, apk, chocolatey, dnf, MacPorts, Nix, pacman, zypper, scoop

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• grafana

Historique du projet

Torkel Odegaard began Grafana as a fork of Kibana while experimenting with ways to query and visualize Graphite data. The first public release, Grafana v1.0, appeared on January 19, 2014 with a Graphite query editor, templating, and dashboard storage through the Kibana 3 base.

Grafana v2 added a Go backend in 2015 so dashboards and users could be stored without relying on Elasticsearch. The project then expanded beyond its Graphite roots into a multi-data-source dashboard system with plugins, alerting, and a long-running commitment to dashboard compatibility.

Grafana Labs' own history of the UX describes v3 and v4 as the period when the plugin system, panel plugins, grafana.net, and alerting became central. Grafana v5 reworked dashboard layout around a grid system, reducing the awkward row model while preserving older dashboards.

Historique d'adoption

Grafana's early adoption came from the Graphite community because it made Graphite queries easier to read and edit and offered interactive dashboards that were more approachable than JSON-only alternatives. That origin explains why package managers adopted it as a developer and operations staple rather than a narrow visualization app.

As Prometheus, Loki, Tempo, Mimir, and OpenTelemetry grew around cloud-native observability, Grafana became the visual layer many teams installed locally or as a service. Homebrew users commonly install it to run dashboards during development, test plugins, or mirror production observability setups.

Modes d'utilisation

A packaged Grafana install usually runs the server executable, reads grafana.ini from the platform config path, and serves dashboards through a web UI. Administrators add data sources, dashboards, users, alert rules, and plugins, while developers often use the package as a local observability workbench.

The bundled Grafana server CLI is a separate administration surface for tasks such as plugin management and admin operations, while grafanactl and gcx address Grafana-as-code workflows outside the server package.

Pourquoi les passionnés de paquets s'y intéressent

Grafana is a classic package-manager heavyweight: a Go service with frontend assets, config files, service definitions, plugin directories, and many downstream integrations. Its packaging tells users where state and config live, how upgrades preserve dashboards, and how the local service joins a larger metrics/logs/traces toolchain.

For package nerds, Grafana also marks the shift from single-purpose time-series graphing tools toward composable observability stacks, where the visualization package is the user-facing hub for several backend packages.

Chronologie

• 2014-01-19: Grafana v1.0 public release.
• 2015: Grafana v2 introduced a Go backend.
• 2016: Grafana v3 introduced a more formal plugin system and grafana.net.
• 2016: Grafana v4 added alerting.
• 2018: Grafana v5 moved dashboards to a new grid layout system.
• 2019: Grafana v6 improved visualization switching and panel editing.

Related projects

• Graphite and Kibana shaped Grafana's origin.
• Prometheus, Loki, Tempo, Mimir, Alloy, and OpenTelemetry are common parts of the same observability stack.
• grafanactl and gcx are related command-line tools for Grafana resource management.

Sources

• https://grafana.com/blog/4-years-of-grafana/
• https://grafana.com/blog/the-mostly-complete-history-of-grafana-ux/
• https://grafana.com/docs/grafana/latest/
• https://grafana.com/docs/grafana/latest/administration/cli/