# Install grizzly with Homebrew, Nix Command-line tool for managing and automating Grafana dashboards. Version 0.7.1 via Homebrew; verified 2026-07-05. ## Install ```sh sudo av install brew:grizzly ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install grizzly ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#grizzly ``` Evidence: nixpkgs package indexes: pkgs/by-name/gr/grizzly/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:grizzly - **Package manager:** Homebrew - **Package manager page:** - **Version:** 0.7.1 - **Source summary:** Command-line tool for managing and automating Grafana dashboards - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-07-05T00:14:30+09:00 - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - grr (cli) - grr (alias) ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 0.7.1 - Package-manager updated: 2026-07-05 - Local data: ok - Upstream repository: https://github.com/grafana-cold-storage/grizzly - Upstream latest detected: v0.7.1 (current) ## Project history and usage Grafana Grizzly is a CLI for managing observability resources as code. It packages a GitOps-style Grafana workflow into the `grr` command, letting teams define dashboards, alerting, and recording rules in files and apply them to Grafana APIs. ### Project history Grizzly came out of the Grafana-as-code ecosystem, where dashboards and related resources moved from UI-only configuration into version-controlled JSON, Jsonnet, and Kubernetes-like YAML. The official repository describes it as a command-line tool for managing observability resources as code and building those updates into deployment pipelines. Grafana's own as-code writing placed Grizzly beside Grafonnet, Terraform, and the Grafana Operator as one of the tools for publishing Git-based dashboard definitions. Later Grafana documentation marked Grizzly as deprecated and directed users toward Grafana CLI workflows. ### Adoption history Grizzly appealed to teams that wanted dashboards and alerts reviewed in pull requests, pushed by CI, and kept near application code. Grafana blog posts used it as an example tool for dashboard-as-code workflows and for reviewing Git-based dashboards locally. The package's adoption was strongest among Grafana and Jsonnet users who wanted a CLI bridge between rendered dashboard definitions and live Grafana instances. ### How it is used Users configure a context with Grafana connection details, then use `grr` commands to apply, get, diff, watch, or serve resources. The settings file can carry both target URLs and authentication material, which is why the package has the same path for configuration and credentials. In package-manager culture it is a small operational binary: install it, point it at Grafana, and wire it into local dashboard development or CI. ### Why package nerds care Grizzly is interesting because it shows observability configuration moving into the same package and Git workflows as application code. It is not a dashboard renderer by itself; it is glue between source-controlled resource definitions and Grafana's APIs. It also shows the lifecycle risk of cloud-infrastructure CLIs. A useful package can become a migration step when its owning platform standardizes around a replacement. ### Timeline - 2020: Grafana described Grizzly as a tool for managing observability resources with code. - 2021: Users discussed Grizzly in CI workflows for generated Grafana dashboards. - 2024: Grafana documented Grizzly in Git-based dashboard editing workflows. - Afterward: Grafana documentation marked Grizzly as removed from active support and pointed users to Grafana CLI. ### Related projects - Grafana is the observability platform Grizzly manages. - Grafonnet and Jsonnet are common dashboard-as-code inputs used with Grizzly-style workflows. - Grafana Terraform provider and Grafana Operator cover adjacent infrastructure-as-code workflows. - grafanactl and Grafana CLI workflows are successors in Grafana's documented direction. ### Sources - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Linux: $XDG_CONFIG_HOME/grizzly/settings.yaml, ~/.config/grizzly/settings.yaml - macOS: ~/Library/Application Support/grizzly/settings.yaml - Windows: %LOCALAPPDATA%\grizzly\settings.yaml ## Credential files - Linux: $XDG_CONFIG_HOME/grizzly/settings.yaml, ~/.config/grizzly/settings.yaml - macOS: ~/Library/Application Support/grizzly/settings.yaml - Windows: %LOCALAPPDATA%\grizzly\settings.yaml ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** grizzly - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** yes - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - Nix - grizzly: normalized package name match | nixpkgs package indexes: pkgs/by-name/gr/grizzly/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Related links - [Cloud CLI packages](https://www.automicvault.com/pkg/cloud-clis/) - Belongs to a cloud or infrastructure command family. - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [mcp-grafana](https://www.automicvault.com/pkg/brew/mcp-grafana/) - Shares av.db curated category or tags: cli, cloud-infrastructure, dashboards, grafana, observability. - [logcli](https://www.automicvault.com/pkg/brew/logcli/) - Shares av.db curated category or tags: cli, cloud-infrastructure, grafana, observability. - [mimirtool](https://www.automicvault.com/pkg/brew/mimirtool/) - Shares av.db curated category or tags: cli, cloud-infrastructure, grafana, observability. - [newrelic-infra-agent](https://www.automicvault.com/pkg/brew/newrelic-infra-agent/) - Shares av.db curated category or tags: cli, cloud-infrastructure, observability. - [sloth-cli](https://www.automicvault.com/pkg/brew/sloth-cli/) - Shares av.db curated category or tags: cli, cloud-infrastructure, observability. - [swctl](https://www.automicvault.com/pkg/brew/swctl/) - Shares av.db curated category or tags: cli, cloud-infrastructure, observability. - [aiac](https://www.automicvault.com/pkg/brew/aiac/) - Shares av.db curated category or tags: cli, cloud-infrastructure, infrastructure-as-code. - [cdk8s](https://www.automicvault.com/pkg/brew/cdk8s/) - Shares av.db curated category or tags: cli, cloud-infrastructure, infrastructure-as-code. - [grizzly](https://www.automicvault.com/pkg/npm/grizzly/) - Same normalized package name in another local ecosystem. ## Combined YAML source View the package source record on GitHub. [combined/grizzly.yml](https://github.com/automic-vault/db/blob/main/combined/grizzly.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph