Grafana Grizzly

https://grafana.github.io/grizzly/
Admin
Grafana Grizzly is a command-line tool for managing Grafana dashboards, data sources, and alerting...
Tokens:8,847
Snippets:127
Trust Score:9.7
Update:5 months ago
Show doc for...
Tokens:
Raw
### Install Grizzly on Linux

Source: https://grafana.github.io/grizzly/installation

Move the downloaded release file to the system's bin directory and make it executable.

```bash
sudo mv $DOWNLOADED_FILE /usr/local/bin/grr
sudo chmod +x /usr/local/bin/grr

```

--------------------------------

### Start the Grizzly Server

Source: https://grafana.github.io/grizzly/server

Starts the Grizzly server on the default port 8080. No resources are available until configured.

```bash
grr serve

```

--------------------------------

### Watch Jsonnet Scripts and Directories

Source: https://grafana.github.io/grizzly/server

Starts the Grizzly server, watching a specific Jsonnet entrypoint and a directory for changes. Useful for multi-file Jsonnet projects.

```bash
grr serve -w examples/grr.jsonnet examples

```

--------------------------------

### Get Grizzly Configuration File Path

Source: https://grafana.github.io/grizzly/configuration

Display the file path of the current Grizzly configuration. This is useful for manual inspection or editing.

```bash
grr config path

```

--------------------------------

### Install Grizzly on macOS via Homebrew

Source: https://grafana.github.io/grizzly/installation

Installs Grizzly using the Homebrew package manager on macOS.

```bash
brew install grizzly

```

--------------------------------

### Get Grizzly Configuration

Source: https://grafana.github.io/grizzly/configuration

Retrieve the configuration for the current context. Specific configuration values can be accessed by appending the key.

```bash
grr config get

```

```bash
grr config get grafana

```

```bash
grr config get grafana.url

```

--------------------------------

### Watch Multiple Jsonnet Sources

Source: https://grafana.github.io/grizzly/server

Starts the Grizzly server, watching multiple Jsonnet source files and directories for changes. Allows for complex project structures.

```bash
grr serve -w examples/grr.jsonnet examples/*.*sonnet examples/vendor

```

--------------------------------

### Get a Specific Resource by UID

Source: https://grafana.github.io/grizzly/workflows

Retrieves a single resource from a remote system using its type and UID. The UID is a two-part identifier separated by a dot, for example, 'dashboard.my-uid'.

```bash
$ grr get Dashboard.my-uid

```

--------------------------------

### Serve Local JSON or YAML Files

Source: https://grafana.github.io/grizzly/server

Starts the Grizzly server to serve specified local JSON or YAML files. Access the server at http://localhost:8080.

```bash
grr serve examples/yaml/

```

--------------------------------

### Watch and Review YAML File Changes

Source: https://grafana.github.io/grizzly/server

Starts the Grizzly server and watches for changes in the specified directory. Reloads dashboards in Grafana automatically when files are modified.

```bash
grr serve -w examples/yaml

```

--------------------------------

### Define a Grafana Dashboard in YAML

Source: https://grafana.github.io/grizzly/what-is-grizzly

A YAML representation of a Grafana dashboard, inspired by Kubernetes resource definitions. This example defines a 'Production Overview' dashboard.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: Dashboard
metadata:
    name: prod-overview
    folder: general
spec:
    schemaVersion: 17
    tags:
        - templated
    timezone: browser
    title: Production Overview
    uid: prod-overview
```

--------------------------------

### Define a Grafana Library Element (Panel)

Source: https://grafana.github.io/grizzly/grafana

Structure a Grafana Library Element, such as a panel or variable. This example shows a text panel with specific content and configuration.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: LibraryElement
metadata:
    name: bcb6ec8a-8a64-4fa6-a490-68b8e73bee16
spec:
    kind: 1 # 1 = Panel, 2 = Variable
    model:
        datasource:
            type: prometheus
            uid: grafanacloud-prom
        description: ""
        gridPos:
            h: 8
            w: 12
            x: 0
            "y": 0
        id: 1
        options:
            code:
                language: plaintext
                showLineNumbers: false
                showMiniMap: false
            content: Example Content
            mode: markdown
        title: Example Panel
        type: text
    name: Example Panel
    orgId: 1
    type: text

```

--------------------------------

### Provision Grafana Notification Template

Source: https://grafana.github.io/grizzly/grafana

Define custom notification templates for alert messages. This example includes templates for title, message, and alert list formatting.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: AlertNotificationTemplate
metadata:
  name: standard-template
spec:
  name: standard-template
  template: |-
    {{ define "default.title.copy" }}
      [{{ .Status | toUpper }}{{ if eq .Status "firing" }}:{{ .Alerts.Firing | len }}{{ if gt (.Alerts.Resolved | len) 0 }}, RESOLVED:{{ .Alerts.Resolved | len }}{{ end }}{{ end }}] {{ .GroupLabels.SortedPairs.Values | join " " }} {{ if gt (len .CommonLabels) (len .GroupLabels) }}({{ with .CommonLabels.Remove .GroupLabels.Names }}{{ .Values | join " " }}{{ end }}){{ end }}
    {{ end }}

    {{ define "default.message.copy" }}{{ if gt (len .Alerts.Firing) 0 }}**Firing**
    {{ template "__text_alert_list.copy" .Alerts.Firing }}{{ if gt (len .Alerts.Resolved) 0 }}

    {{ end }}{{ end }}{{ if gt (len .Alerts.Resolved) 0 }}**Resolved**
    {{ template "__text_alert_list.copy" .Alerts.Resolved }}{{ end }}{{ end }}

    {{ define "__text_alert_list.copy" }}{{ range . }}    Value: {{ template "__text_values_list.copy" . }}
    Labels:
    {{ range .Labels.SortedPairs }} - {{ .Name }} = {{ .Value }}
    {{ end }}Annotations:
    {{ range .Annotations.SortedPairs }} - {{ .Name }} = {{ .Value }}
    {{ end }}{{ if gt (len .GeneratorURL) 0 }}Source: {{ .GeneratorURL }}
    {{ end }}{{ if gt (len .SilenceURL) 0 }}Silence: {{ .SilenceURL }}
    {{ end }}{{ if gt (len .DashboardURL) 0 }}Dashboard: {{ .DashboardURL }}
    {{ end }}{{ if gt (len .PanelURL) 0 }}Panel: {{ .PanelURL }}
    {{ end }}{{ end }}{{ end }}

    {{ define "__text_values_list.copy" }}{{ if len .Values }}{{ $first := true }}{{ range $refID, $value := .Values -}}
    {{ if $first }}{{ $first = false }}{{ else }}, {{ end }}{{ $refID }}={{ $value }}{{ end -}}
    {{ else }}[no value]{{ end }}{{ end }}

```

--------------------------------

### Define a Grafana Alert Rule Group

Source: https://grafana.github.io/grizzly/grafana

Configure an AlertRuleGroup in Grafana, which comprises a set of rules evaluated at the same interval. This example includes rule conditions, data sources, and state configurations.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: AlertRuleGroup
metadata:
    name: fee4037a-b193-4e28-9330-2cc9028b048c.d
spec:
    folderUid: fee4037a-b193-4e28-9330-2cc9028b048c
    interval: 180 # in seconds
    rules:
        - condition: B
          data:
            - datasourceUid: grafanacloud-demoinfra-prom
              model:
                datasource:
                    type: prometheus
                    uid: grafanacloud-demoinfra-prom
                editorMode: code
                expr: weather_temp_c{location="Vienna"}
                instant: true
                intervalMs: 1000
                legendFormat: __auto
                maxDataPoints: 43200
                range: false
                refId: A
              refId: A
              relativeTimeRange:
                from: 600
            - datasourceUid: __expr__
              model:
                conditions:
                    - evaluator:
                        params:
                            - 30
                        type: gt
                      operator:
                        type: and
                      query:
                        params:
                            - C
                      reducer:
                        params: []
                        type: last
                      type: query
                datasource:
                    type: __expr__
                    uid: __expr__
                expression: A
                intervalMs: 1000
                maxDataPoints: 43200
                refId: B
                type: threshold
              refId: B
              relativeTimeRange:
                from: 600
          execErrState: Error
          folderUID: fee4037a-b193-4e28-9330-2cc9028b048c
          for: 5m0s
          id: 3
          noDataState: NoData
          orgID: 1
          ruleGroup: d
          title: Temperature high
          uid: d4231da1-2456-4741-8a81-527167a96b69
spec:
    title: Alert Group Europe

```

--------------------------------

### Build Grizzly from Source

Source: https://grafana.github.io/grizzly/installation

Clones the Grizzly repository, navigates into the directory, builds the development version, and moves the executable to the system's bin directory.

```bash
git clone https://github.com/grafana/grizzly.git
cd grizzly
make dev
sudo mv grr /usr/local/bin/grr

```

--------------------------------

### List Resources with Different Output Formats

Source: https://grafana.github.io/grizzly/workflows

Lists resources from a directory with customizable output formats. Supported formats include 'default', 'wide', 'yaml', and 'json'.

```bash
$ grr list -f yaml my-dir

```

--------------------------------

### Show Rendered Resources

Source: https://grafana.github.io/grizzly/workflows

Displays the resources generated by executing Jsonnet files, formatted appropriately for each resource type.

```bash
$ grr show my-dir

```

--------------------------------

### Set Resource Targets

Source: https://grafana.github.io/grizzly/workflows

Allows targeting specific resources by key, in the format '<type>.<uid>'. Wildcards like 'Dashboard.*' are supported. If no '.' is present, it matches the resource type only. Lowercase names are also accepted for type matching.

```bash
$ grr list

```

--------------------------------

### Deploy Resources as Snapshots

Source: https://grafana.github.io/grizzly/workflows

Deploys resources as snapshots, currently supporting only Grafana dashboards. The command prints out links for each uploaded snapshot. Expiration can be configured using the '-e' flag.

```bash
$ grr snapshot my-lib.libsonnet

```

--------------------------------

### Import Environment Variables into Default Context

Source: https://grafana.github.io/grizzly/configuration

Import environment variables into the `default` context. Ensure environment variables are configured before running.

```bash
grr config import

```

--------------------------------

### List Resources in a Directory

Source: https://grafana.github.io/grizzly/workflows

Lists all resources found after executing a Jsonnet file within a specified directory.

```bash
$ grr list my-dir

```

--------------------------------

### List Existing Grizzly Contexts

Source: https://grafana.github.io/grizzly/configuration

Display all configured Grizzly contexts. This command helps in managing multiple environments.

```bash
grr config get-contexts

```

--------------------------------

### Configure Hosted Prometheus/Mimir Settings

Source: https://grafana.github.io/grizzly/configuration

Set the URL, tenant ID, and API key for interacting with hosted Prometheus or Grafana Mimir instances. The API key is required for Grafana Cloud.

```bash
grr config set mimir.address https://mimir.example.com
```

```bash
grr config set mimir.tenant-id myTenant
```

```bash
grr config set mimir.api-key abcdef12345
```

--------------------------------

### Diff Resources with Remote System

Source: https://grafana.github.io/grizzly/workflows

Compares resources rendered by Jsonnet with their corresponding versions on the remote system. This helps identify discrepancies before applying changes.

```bash
$ grr diff my-lib.libsonnet

```

--------------------------------

### Push Resources (Alias for Apply)

Source: https://grafana.github.io/grizzly/workflows

An alias for the 'apply' command, used to push resources to Grafana.

```bash
$ grr push my-lib.libsonnet

```

--------------------------------

### Apply Resources to Grafana

Source: https://grafana.github.io/grizzly/workflows

Uploads resources rendered by a Jsonnet mixin to Grafana. This is the primary command for deploying configurations.

```bash
$ grr apply my-lib.libsonnet

```

--------------------------------

### Create a New Grizzly Context

Source: https://grafana.github.io/grizzly/configuration

Create a new context for managing different Grizzly configurations. Specify the desired context name.

```bash
grr config create-context production

```

--------------------------------

### Watch Directory for Changes and Apply

Source: https://grafana.github.io/grizzly/workflows

Monitors a specified directory for file changes. Upon detecting changes, it executes the associated Jsonnet file and pushes the updated resources to remote systems. Note that newly added subdirectories are not automatically watched.

```bash
$ grr watch . my-lib.libsonnet

```

--------------------------------

### Export Rendered Resources to Files

Source: https://grafana.github.io/grizzly/workflows

Renders Jsonnet files and saves the resulting resources into a specified directory. This is useful for provisioning Grafana dashboards that can be immediately picked up by Grafana.

```bash
$ grr export some-mixin.libsonnet my-provisioning-dir

```

--------------------------------

### Apply a Dashboard to Grafana

Source: https://grafana.github.io/grizzly/what-is-grizzly

Upload a dashboard defined in a YAML file to your Grafana instance using the `grr apply` command.

```bash
$ grr apply dashboard.yaml
Dashboard/prod-overview added
```

--------------------------------

### Create Grizzly Grafana Context

Source: https://grafana.github.io/grizzly/what-is-grizzly

Configure Grizzly to authenticate with your Grafana instance by creating a context and setting the Grafana URL and a service account token.

```bash
grr config create-context instance
grr config set grafana.url http://localhost:3000
grr config set grafana.token <my-service-account-token>
```

--------------------------------

### List Remote Resources

Source: https://grafana.github.io/grizzly/workflows

Lists remote resources across all configured providers. This command is useful for inspecting resources directly from Grafana instances without local files.

```bash
$ grr list -r

```

--------------------------------

### Render Prometheus Rules with Jsonnet

Source: https://grafana.github.io/grizzly/jsonnet

Define a reusable function for creating PrometheusRuleGroup resources and then use it to define alert and recording rules. Elements defined with '::' are hidden from the output unless referenced.

```jsonnet
{
  local rule(name, namespace, spec) = {
    apiVersion: 'grizzly.grafana.com/v1alpha1',
    kind: 'PrometheusRuleGroup',
    metadata: {
      name: name,
      namespace: namespace,
    },
    spec: spec,
  },

  grizzly_alerts:: {
    rules: [{
      alert: 'PromScrapeFailed',
      expr: 'up != 1',
      'for': '1m',
      labels: {
        severity: 'critical',
      },
      annotations: {
        message: 'Prometheus failed to scrape a target {{ $labels.job }}  / {{ $labels.instance }}',
      },
    }],
  },

  grizzly_records:: {
    rules: [{
      record: 'job:up:sum',
      expr: 'sum by(job) (up)',
    }],
  },

  prometheus_rules: [
    rule('grizzly_alert_rules', 'grizzly_rules', $.grizzly_alerts),
    rule('grizzly_recording_rules', 'grizzly_rules', $.grizzly_records),
  ],
}

```

--------------------------------

### Push Dashboards and Folders to Destination Grafana

Source: https://grafana.github.io/grizzly/workflows

Configure Grizzly to push dashboards and folders to a destination Grafana instance. Set the destination Grafana URL and token, specify 'Dashboard,Dashboardfolder' as targets, and use JSON output format.

```bash
$ grr config create-context destination
$ grr config set grafana.url <...destination Grafana URL...>
$ grr config set grafana.token <...destination Grafana service account token...>
$ grr config set targets Dashboard,Dashboardfolder
$ grr config set output-format json
$ grr push resources

```

--------------------------------

### Configure Grafana Synthetic Monitoring

Source: https://grafana.github.io/grizzly/configuration

Set the access token and URL for interacting with Grafana Synthetic Monitoring. These details can be found in the Synthetic Monitoring plugin's configuration page in Grafana.

```bash
grr config set synthetic-monitoring.access-token abcdef123456
```

```bash
grr config set synthetic-monitoring.url https://synthetic-monitoring-api.grafana.net
```

--------------------------------

### Define a Grafana Dashboard Folder

Source: https://grafana.github.io/grizzly/grafana

Use this to create a simple Grafana dashboard folder. Specify the metadata name and the desired title for the folder.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: DashboardFolder
metadata:
  name: sample
spec:
  title: Special Sample Folder

```

--------------------------------

### Configure Output Format

Source: https://grafana.github.io/grizzly/configuration

Set the output format for resources retrieved from Grafana. Supported formats are JSON and YAML (default). This can be overridden on the command line with -o or --output.

```bash
grr config set output-format json
```

--------------------------------

### Place a Dashboard in a Specific Folder

Source: https://grafana.github.io/grizzly/grafana

Assign a dashboard to a specific folder using the `folder` metadata field. The 'general' folder is a special case and can be referenced directly.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: Dashboard
metadata:
    folder: sample
    name: prod-overview
spec:
    schemaVersion: 17
    tags:
        - templated
    timezone: browser
    title: Production Overview
    uid: prod-overview

```

--------------------------------

### Provision Grafana Email Contact Point

Source: https://grafana.github.io/grizzly/grafana

Use this structure to provision an email contact point in Grafana. Ensure the `uid` matches the `metadata.name` for consistency.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: AlertContactPoint
metadata:
    name: eaae236a-7be9-4748-a08e-54b92ffb2e60
spec:
    name: grafana-default-email
    settings:
        addresses: <example@email.com>
        singleEmail: false
    type: email
    uid: eaae236a-7be9-4748-a08e-54b92ffb2e60

```

--------------------------------

### Set Grafana URL

Source: https://grafana.github.io/grizzly/configuration

Configure the root URL for your Grafana instance. This is a minimum requirement for Grizzly to interact with Grafana.

```bash
grr config set grafana.url http://localhost:3000
```

--------------------------------

### Configure Target Resource Types

Source: https://grafana.github.io/grizzly/configuration

Set a list of resource types that Grizzly should interact with. This can be overridden on the command line using the -t or --target flag.

```bash
grr config set targets Dashboard,DashboardFolder
```

--------------------------------

### Pull Dashboards and Folders from Source Grafana

Source: https://grafana.github.io/grizzly/workflows

Configure Grizzly to pull dashboards and folders from a source Grafana instance. Ensure the source Grafana URL and token are set, and specify 'Dashboard,Dashboardfolder' as targets. The output format is set to JSON.

```bash
$ grr config create-context source
$ grr config set grafana.url <...source Grafana URL...>
$ grr config set grafana.token <...source Grafana service account token...>
$ grr config set targets Dashboard,Dashboardfolder
$ grr config set output-format json
$ grr pull resources

```

--------------------------------

### Show Current Grizzly Context

Source: https://grafana.github.io/grizzly/configuration

Display the name of the currently active Grizzly context. Useful for verifying the active configuration.

```bash
grr config current-context

```

--------------------------------

### Set Grafana Token or Basic Auth Password

Source: https://grafana.github.io/grizzly/configuration

Authenticate with a Grafana instance using a service account token or a basic authentication password. Ensure the service account has appropriate roles.

```bash
grr config set grafana.token abcd12345
```

--------------------------------

### Define Grafana Dashboard Folder and Dashboards

Source: https://grafana.github.io/grizzly/hidden-elements

Use hidden elements to specify a Grafana dashboard folder and add dashboards to it. The key within `grafanaDashboards` is ignored by Grizzly.

```jsonnet
{ 
  grafanaDashboardFolder:: 'sample',
  grafanaDashboards+:: {
    'my-dash.json': {
      uid: 'prod-overview',
      title: 'Production Overview',
      tags: ['templated'],
      timezone: 'browser',
      schemaVersion: 17,
    },
  },
}

```

--------------------------------

### Define a Grafana Datasource

Source: https://grafana.github.io/grizzly/grafana

Configure a Grafana datasource by specifying its access method, URL, and other relevant details.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: Datasource
metadata:
    name: prometheus
spec:
    access: proxy
    url: http://localhost/prometheus/

```

--------------------------------

### Configure 'Only Spec' Output

Source: https://grafana.github.io/grizzly/configuration

Control whether Grizzly wraps resources in an envelope. Setting 'only-spec' to true removes the envelope, providing only the spec component. This can be overridden with the -s or --only-spec=false command-line flags.

```bash
grr config set only-spec true
```

--------------------------------

### Define Prometheus Rules Without Namespace

Source: https://grafana.github.io/grizzly/hidden-elements

Load Prometheus alerts and recording rules without specifying a namespace. Grizzly will default to the `grizzly_rules` namespace in this case.

```jsonnet
{ 
  grizzly_alert:: {
    alert: 'PromScrapeFailed',
    expr: 'up != 1',
    'for': '1m',
    labels: {
      severity: 'critical',
    },
    annotations: {
      message: 'Prometheus failed to scrape a target {{ $labels.job }}  / {{ $labels.instance }}',
    },
  },

  prometheusAlerts+:: {
      // namespace removed
      groups: [{
        name: 'grizzly_alert_rules',
        rules: [
          $.grizzly_alert,
        ],
      }],
  },

  grizzly_record:: {
    record: 'job:up:sum',
    expr: 'sum by(job) (up)',
  },

  prometheusRules+:: {
      // namespace removed
      groups: [{
        name: 'grizzly_recording_rules',
        rules: [
          $.grizzly_record,
        ],
      }],
  },
}

```

--------------------------------

### Define Prometheus Alert and Recording Rules

Source: https://grafana.github.io/grizzly/hidden-elements

Define Prometheus alert and recording rules using hidden elements. Alerts are added to `prometheusAlerts` and recording rules to `prometheusRules`, with a specified namespace.

```jsonnet
{ 
  grizzly_alert:: {
    alert: 'PromScrapeFailed',
    expr: 'up != 1',
    'for': '1m',
    labels: {
      severity: 'critical',
    },
    annotations: {
      message: 'Prometheus failed to scrape a target {{ $labels.job }}  / {{ $labels.instance }}',
    },
  },

  prometheusAlerts+:: {
    grizzly_rules: {
      groups: [{
        name: 'grizzly_alert_rules',
        rules: [
          $.grizzly_alert,
        ],
      }],
    },
  },

  grizzly_record:: {
    record: 'job:up:sum',
    expr: 'sum by(job) (up)',
  },

  prometheusRules+:: {
    grizzly_rules: {
      groups: [{
        name: 'grizzly_recording_rules',
        rules: [
          $.grizzly_record,
        ],
      }],
    },
  },
}

```

--------------------------------

### Define Prometheus Recording Rule Group

Source: https://grafana.github.io/grizzly/prometheus

Use this snippet to define a group of Prometheus recording rules. Ensure the PrometheusRuleGroup is placed in a namespace.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: PrometheusRuleGroup
metadata:
    name: grizzly_recording_rules
    namespace: grizzly_rules
spec:
    rules:
        - expr: sum by(job) (up)
          record: job:up:sum

```

--------------------------------

### Diff Dashboard Changes with Grafana

Source: https://grafana.github.io/grizzly/what-is-grizzly

Compare a local dashboard definition in YAML with the version currently in Grafana using the `grr diff` command. This shows what changes will be applied.

```diff
$ grr diff dashboard.yaml
--- Remote
+++ Local
@@ -4,7 +4,7 @@
     folder: general
     name: prod-overview
 spec:
-    schemaVersion: 17
+    schemaVersion: 18
     tags:
         - templated
     timezone: browser
```

--------------------------------

### Define Prometheus Alert Rule Group

Source: https://grafana.github.io/grizzly/prometheus

Use this snippet to define a group of Prometheus alert rules. Ensure the PrometheusRuleGroup is placed in a namespace.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: PrometheusRuleGroup
metadata:
    name: grizzly_alerts
    namespace: grizzly_rules
spec:
    rules:
        - alert: PromScrapeFailed
          annotations:
            message: Prometheus failed to scrape a target {{ $labels.job }}  / {{ $labels.instance }}
          expr: up != 1
          for: 1m
          labels:
            severity: critical

```

--------------------------------

### Set Grafana Username for Basic Auth

Source: https://grafana.github.io/grizzly/configuration

Optionally, set the username for basic authentication with Grafana. This is used in conjunction with a password or token.

```bash
grr config set grafana.user admin
```

--------------------------------

### Apply Updated Dashboard to Grafana

Source: https://grafana.github.io/grizzly/what-is-grizzly

Apply the changes made to a dashboard definition file to your Grafana instance using the `grr apply` command after reviewing with `grr diff`.

```bash
$ grr apply dashboard.yaml
Dashboard/prod-overview updated
```

--------------------------------

### Switch to a Different Grizzly Context

Source: https://grafana.github.io/grizzly/configuration

Change the active Grizzly context to a different one. Future `grr` commands will use the settings from the selected context.

```bash
grr config use-context staging

```

--------------------------------

### Define a Nested Grafana Dashboard Folder

Source: https://grafana.github.io/grizzly/grafana

Create a nested folder by specifying the parent folder's UID in the `parentUid` field. This ensures proper hierarchy within Grafana.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: DashboardFolder
metadata:
  name: nestedFolderSample
spec:
  parentUid: sample
  title: Nested folder

```

--------------------------------

### Watch TypeScript Code Changes

Source: https://grafana.github.io/grizzly/server

Sets up Grizzly to watch TypeScript files and execute an npm script on changes. This is for reviewing dashboards generated from other languages.

```bash
git clone https://github.com/grafana/grafana-foundation-sdk
cd grafana-foundation-sdk/examples/typescript/red-method
npm install
grr serve -w -S 'npm run -s dev' .

```

--------------------------------

### Define a Synthetic Monitoring HTTP Check

Source: https://grafana.github.io/grizzly/synthetic-monitoring

This YAML defines a Synthetic Monitoring check for an HTTP endpoint. Ensure the 'type' is specified in metadata for uniqueness, especially when reusing names across different check types. The 'probes' field lists the locations from which the check will be performed.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: SyntheticMonitoringCheck
metadata:
    name: grafana-com
    type: http
spec:
    alertSensitivity: ""
    basicMetricsOnly: true
    enabled: true
    frequency: 60000
    job: grafana-com
    labels: []
    offset: 0
    probes:
        - Atlanta
        - Chicago
        - LosAngeles
        - Miami
        - Seattle
        - SanJose
        - Paris
        - Tokyo
        - Seol
        - NewYork
        - SanFrancisco
        - Amsterdam
        - Singapore
        - Frankfurt
        - Bangalore
        - Dallas
        - Newark
        - Toronto
        - London
        - Mumbai
        - Sydney
    settings:
        http:
            failIfNotSSL: false
            failIfSSL: false
            ipVersion: V4
            method: GET
            noFollowRedirects: false
    target: https://google.com/
    timeout: 2500

```

--------------------------------

### Provision Grafana Notification Policy

Source: https://grafana.github.io/grizzly/grafana

Provision a single global notification policy. This CRD defines routing rules and receivers for alerts.

```yaml
apiVersion: grizzly.grafana.com/v1alpha1
kind: AlertNotificationPolicy
metadata:
  name: global
spec:
  group_by:
    - grafana_folder
    - alertname
  receiver: grafana-default-email
  routes:
    - group_by:
        - region
      object_matchers:
        - - foo
          - =
          - bar
      receiver: grafana-oncall

```
Tokens:
Raw