### Complete Grafana Docker Setup Example

Source: https://grafana.com/docs/grafana/latest/setup-grafana/installation/docker

A comprehensive example demonstrating the setup of Grafana in Docker. It includes creating persistent storage, mapping ports, setting a server root URL, and pre-installing a plugin.

```bash
# create a persistent volume for your data
docker volume create grafana-storage

# start grafana by using the above persistent storage
# and defining environment variables

docker run -d -p 3000:3000 --name=grafana \
  --volume grafana-storage:/var/lib/grafana \
  -e "GF_SERVER_ROOT_URL=http://my.grafana.server/" \
  -e "GF_PLUGINS_PREINSTALL=grafana-clock-panel" \
  grafana/grafana-enterprise
```

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

### Start Grafana Server using Binary

Source: https://grafana.com/docs/grafana/latest/installation/restart-grafana

Execute the Grafana binary directly from its installation directory to start the server. Ensure the working directory is set correctly.

```bash
./bin/grafana server
```

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

### Install Grafana Foundation SDK for Go

Source: https://grafana.com/docs/grafana/latest/as-code/observability-as-code/foundation-sdk

Install the Grafana Foundation SDK for Go using the go get command. Ensure you have Go installed and configured.

```go
go get github.com/grafana/grafana-foundation-sdk/go@latest
```

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

### Example Response for Get Users

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/api-legacy/org

Example of a successful response when retrieving users from an organization.

```http
HTTP/1.1 200
Content-Type: application/json
[
  {
    "orgId":1,
    "userId":1,
    "email":"admin@mygraf.com",
    "login":"admin",
    "role":"Admin"
  }
]
```

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

### Example Response for Get all library elements

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/api-legacy/library_element

This is an example of a successful response (HTTP 200) when retrieving library elements. It includes total count, pagination details, and a list of elements with their metadata.

```json
HTTP/1.1 200
Content-Type: application/json

{
  "result": {
     "totalCount": 15,
     "page": 1,
     "perPage": 10
     "elements": [
        {
            "id": 25,
            "orgId": 1,
            "folderId": 0,
            "uid": "V--OrYHnz",
            "name": "API docs Example",
            "kind": 1,
            "type": "text",
            "description": "",
            "model": {...},
            "version": 1,
            "meta": {
                "folderName": "General",
                "folderUid": "",
                "connectedDashboards": 1,
                "created": "2021-09-27T09:56:17+02:00",
                "updated": "2021-09-27T09:56:17+02:00",
                "createdBy": {
                    "id": 1,
                    "name": "admin",
                    "avatarUrl": "/avatar/46d229b033af06a191ff2267bca9ae56"
                },
                "updatedBy": {
                    "id": 1,
                    "name": "admin",
                    "avatarUrl": "/avatar/46d229b033af06a191ff2267bca9ae56"
                }
            }
        },
        {...}
        {...}
     ],
  }
}
```

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

### Example Response for Get Folder

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/folder

Illustrates a successful response when retrieving a folder, including its metadata and specifications.

```json
HTTP/1.1 200
Content-Type: application/json
{
  "kind": "Folder",
  "apiVersion": "folder.grafana.app/v1",
  "metadata": {
    "name": "aef30vrzxs3y8d",
    "namespace": "default",
    "uid": "KCtv1FXDsJmTYQoTgcPnfuwZhDZge3uMpXOefaOHjb4X",
    "resourceVersion": "1741343686000",
    "creationTimestamp": "2025-03-07T10:34:46Z",
    "annotations": {
      "grafana.app/createdBy": "service-account:cef2t2rfm73lsb",
      "grafana.app/updatedBy": "service-account:cef2t2rfm73lsb",
      "grafana.app/updatedTimestamp": "2025-03-07T10:34:46Z",
      "grafana.app/folder": "fef30w4jaxla8b"
    }
  },
  "spec": {
    "title": "test"
  }
}
```

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

### Install Traces Drilldown Plugin in Docker Container

Source: https://grafana.com/docs/grafana/latest/visualizations/simplified-exploration/traces/access

Configure this environment variable within your Docker setup to automatically install the Traces Drilldown plugin when the container starts. This is useful for automated deployments.

```shell
GF_INSTALL_PLUGINS=grafana-exploretraces-app
```

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

### Prometheus Service ExecStart Configuration Example

Source: https://grafana.com/docs/grafana/latest/fundamentals/getting-started/first-dashboards/get-started-grafana-prometheus

Example of the ExecStart line in a Prometheus systemd service file. Verify the binary path, config file path, and storage path.

```bash
ExecStart=/usr/local/bin/prometheus --config.file=/etc/prometheus/prometheus.yml --storage.tsdb.path=/var/lib/prometheus/
```

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

### List Plugins HTTP Request

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/cloud-api

This example shows the HTTP GET request to retrieve a list of plugins installed on a Grafana Cloud instance. Ensure you replace `<STACK_SLUG>` with your stack's identifier.

```http
GET https://grafana.com/api/instances/<STACK_SLUG>/plugins
```

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

### Get Installed Plugin Info (HTTP GET)

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/cloud-api

Retrieve information about a specific plugin installed on your Grafana Cloud instance. Requires the stack slug and plugin identifier.

```http
GET https://grafana.com/api/instances/<STACK_SLUG>/plugins/<PLUGIN>
```

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

### Provision Plugin Configuration

Source: https://grafana.com/docs/grafana/latest/administration/provisioning

This example shows how to provision a plugin's configuration using a YAML file. Ensure the plugin is already installed before provisioning its configuration.

```yaml
apiVersion: 1

apps:
  # <string> the type of app, plugin identifier. Required
  - type: raintank-worldping-app
    # <int> Org ID. Default to 1, unless org_name is specified
    org_id: 1
    # <string> Org name. Overrides org_id unless org_id not specified
    org_name: Main Org.
    # <bool> disable the app. Default to false.
    disabled: false
    # <map> fields that will be converted to json and stored in jsonData. Custom per app.
    jsonData:
      # key/value pairs of string to object
      key: value
    # <map> fields that will be converted to json, encrypted and stored in secureJsonData. Custom per app.
    secureJsonData:
      # key/value pairs of string to string
      key: value
```

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

### Example: Grafana with Pre-installed Plugin and Custom URL

Source: https://grafana.com/docs/grafana/latest/setup-grafana/installation/docker

This `docker-compose.yaml` example demonstrates running the latest Grafana, setting a server root URL, and pre-installing the clock panel plugin. It uses Docker volumes for persistent storage.

```yaml
services:
  grafana:
    image: grafana/grafana-enterprise
    container_name: grafana
    restart: unless-stopped
    environment:
      - GF_SERVER_ROOT_URL=http://my.grafana.server/
      - GF_PLUGINS_PREINSTALL=grafana-clock-panel
    ports:
      - '3000:3000'
    volumes:
      - 'grafana_storage:/var/lib/grafana'
volumes:
  grafana_storage: {}
```

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

### Get Dashboard Example

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/apis

Example of how to retrieve a specific dashboard using its namespace and name.

```APIDOC
## GET /apis/dashboard.grafana.app/v1/namespaces/{namespace}/dashboards/{name}

### Description
Retrieves a specific dashboard by its namespace and name.

### Method
GET

### Endpoint
/apis/dashboard.grafana.app/v1/namespaces/{namespace}/dashboards/{name}

### Parameters
#### Path Parameters
- **namespace** (string) - Required - The namespace of the dashboard.
- **name** (string) - Required - The name of the dashboard.

### Response
#### Success Response (200)
- **kind** (string) - The resource kind, e.g., "Dashboard".
- **apiVersion** (string) - The API version.
- **metadata** (object) - Contains metadata about the dashboard, including name, namespace, uid, resourceVersion, generation, creationTimestamp, annotations, and labels.
- **spec** (object) - The desired state of the dashboard.
```

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

### Complete example for app and page navigation placement

Source: https://grafana.com/docs/grafana/latest/administration/plugin-management/customize-nav-bar

This example demonstrates configuring both the placement of an entire app plugin and individual app pages within the Grafana navigation. Ensure correct syntax and restart Grafana for changes to take effect.

```ini
# Move the entire app to the Explore section
[navigation.app_sections]
org-example-app = explore 50

# Move specific pages to their own sections
[navigation.app_standalone_pages]
/a/org-example-app/metrics = dashboards 100
/a/org-example-app/logs = alerting 75
```

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

### Get installed plugin info

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/cloud-api

Retrieves information about a specific plugin installed on a Grafana Cloud instance.

```APIDOC
## GET https://grafana.com/api/instances/<STACK_SLUG>/plugins/<PLUGIN>

### Description
Retrieves information about a specific plugin installed on a Grafana Cloud instance.

### Method
GET

### Endpoint
https://grafana.com/api/instances/<STACK_SLUG>/plugins/<PLUGIN>

### Response
#### Success Response (200)
- **id** (integer) - Unique identifier for the plugin installation.
- **instanceId** (integer) - The ID of the Grafana Cloud instance.
- **instanceUrl** (string) - The URL of the Grafana Cloud instance.
- **instanceSlug** (string) - The slug of the Grafana Cloud instance.
- **pluginId** (integer) - The internal ID of the plugin.
- **pluginSlug** (string) - The slug of the plugin.
- **pluginName** (string) - The name of the plugin.
- **version** (string) - The installed version of the plugin.
- **latestVersion** (string) - The latest available version of the plugin.
- **createdAt** (string) - Timestamp when the plugin was installed.
- **updatedAt** (string) - Timestamp when the plugin was last updated (null if never updated).
- **links** (array) - Links related to the plugin installation.

### Response Example
```json
{
  "id": 256519,
  "instanceId": 507363,
  "instanceUrl": "https://createcloudstack.grafana.net",
  "instanceSlug": "createcloudstack",
  "pluginId": 663,
  "pluginSlug": "grafana-github-datasource",
  "pluginName": "GitHub",
  "version": "1.3.1",
  "latestVersion": "1.3.1",
  "createdAt": "2023-01-04T08:50:42.000Z",
  "updatedAt": null,
  "links": [
    {
      "rel": "self",
      "href": "/instances/createcloudstack/plugins/grafana-github-datasource"
    },
    {
      "rel": "instance",
      "href": "/instances/createcloudstack"
    }
  ]
}
```
```

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

### Examples of CPU Metric Queries with Dynamic Filtering

Source: https://grafana.com/docs/grafana/latest/dashboards/variables/add-template-variables

These examples illustrate potential queries for CPU metrics based on user selections for datacenter and host. They show how different combinations of selected values translate into specific queries.

```bash
SHOW TAG VALUES WITH KEY = "cpu" WHERE "datacenter" =~ /^America/ AND "host" =~ /^server2/
SHOW TAG VALUES WITH KEY = "cpu" WHERE "datacenter" =~ /^Africa/ AND "host" =~ /^server/7/
SHOW TAG VALUES WITH KEY = "cpu" WHERE "datacenter" =~ /^Europe/ AND "host" =~ /^server3+server4/
```

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

### Enable Grafana Server to Start at Boot with init.d

Source: https://grafana.com/docs/grafana/latest/installation/restart-grafana

Configure the Grafana server to automatically start when the system boots up using the init.d method.

```bash
sudo update-rc.d grafana-server defaults
```

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

### Example Mute Timings Response

Source: https://grafana.com/docs/grafana/latest/alerting/set-up/provision-alerting-resources/http-api-provisioning

An example JSON response for a GET request to retrieve mute timings.

```json
HTTP/1.1 200 OK
Content-Type: application/json

[
  {
    "name": "weekends",
    "time_intervals": [
      {
        "weekdays": [
          "saturday",
          "sunday"
        ]
      }
    ],
    "version": "",
    "provenance": "file"
  }
]
```

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

### Install grafanactl from Source

Source: https://grafana.com/docs/grafana/latest/as-code/observability-as-code/grafana-cli/grafanactl

Build the grafanactl CLI from source using Go. Ensure you have git and Go v1.24 or greater installed.

```bash
go install github.com/grafana/grafanactl/cmd/grafanactl@latest
```

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

### Install Plugin from Local URL

Source: https://grafana.com/docs/grafana/latest/administration/cli

Use the --pluginUrl option to install a plugin by providing a direct URL to its .zip file.

```bash
grafana cli --pluginUrl https://company.com/grafana/plugins/<plugin-id>-<plugin-version>.zip plugins install <plugin-id>
```

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

### Example Template Query

Source: https://grafana.com/docs/grafana/latest/dashboards/variables

This is an example of a template query that uses variables. Queries with text starting with '$' are considered templates.

```text
groupByNode(movingAverage(apps.$app.$server.counters.requests.count, 10), 2, 'sum')
```

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

### GET /api/frontend/settings Response

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/api-legacy/other

Example response for the GET /api/frontend/settings endpoint, detailing frontend configuration and build information.

```json
HTTP/1.1 200
Content-Type: application/json

{
  "allowOrgCreate":true,
  "appSubUrl":"",
  "buildInfo":{
    "buildstamp":xxxxxx,
    "commit":"vyyyy",
    "version":"zzzzz"
  },
  "datasources":{
    "datasourcename":{
      "index":"grafana-dash",
      "meta":{
        "annotations":true,
        "module":"plugins/datasource/grafana/datasource",
        "name":"Grafana",
        "partials":{
          "annotations":"app/plugins/datasource/grafana/partials/annotations.editor.html",
          "config":"app/plugins/datasource/grafana/partials/config.html"
        },
        "pluginType":"datasource",
        "serviceName":"Grafana",
        "type":"grafanasearch"
      }
    }
  },
  "defaultDatasource": "Grafana"
}
```

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

### YAML Configuration Example

Source: https://grafana.com/docs/grafana/latest/setup-grafana/image-rendering/flags

Example of a complete configuration file in YAML format for the image rendering service. It demonstrates setting the server address and authentication tokens.

```yaml
server:
  addr: ":8081" # server.addr
  auth-token: # server.auth-token
    - "a"
    - "b"
```

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

### Cascading Filter Example: Parent Variable

Source: https://grafana.com/docs/grafana/latest/datasources/opentsdb/template-variables

Example of creating a parent template variable for a cascading filter setup.

```none
tag_values(sys.cpu.user, datacenter)
```

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

### Example Decryption of Support Bundle

Source: https://grafana.com/docs/grafana/latest/troubleshooting/support-bundles

An example demonstrating the decryption of a specific support bundle file using a provided key and output file name.

```bash
age --decrypt -i key.txt -o data.tar.gz af6684b4-d613-4b31-9fc3-7cb579199bea.tar.gz.age
```

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

### Get Reports Branding Settings Request

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/api-legacy/reporting

Example of an HTTP GET request to retrieve the global branding settings for reports.

```http
GET /api/reports/settings HTTP/1.1
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
```

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

### Tempo Data Source Provisioning Example

Source: https://grafana.com/docs/grafana/latest/datasources/tempo/configure-tempo-data-source/provision

Use this YAML configuration to provision the Tempo data source. Ensure you replace placeholder UIDs with your actual data source UIDs and adjust settings as needed.

```yaml
apiVersion: 1

datasources:
  - name: Tempo
    type: tempo
    uid: EbPG8fYoz
    url: http://localhost:3200
    access: proxy
    basicAuth: false
    jsonData:
      tracesToLogsV2:
        # Field with an internal link pointing to a logs data source in Grafana.
        # datasourceUid value must match the uid value of the logs data source.
        datasourceUid: 'loki'
        spanStartTimeShift: '-1h'
        spanEndTimeShift: '1h'
        tags: [{ key: 'job' }, { key: 'instance' }, { key: 'pod' }, { key: 'namespace' }]
        filterByTraceID: false
        filterBySpanID: false
        customQuery: true
        query: 'method="$${__span.tags.method}"'
      tracesToMetrics:
        datasourceUid: 'prom'
        spanStartTimeShift: '-1h'
        spanEndTimeShift: '1h'
        tags: [{ key: 'service.name', value: 'service' }, { key: 'job' }]
        queries:
          - name: 'Sample query'
            query: 'sum(rate(traces_spanmetrics_latency_bucket{$$__tags}[5m]))'
      tracesToProfiles:
        datasourceUid: 'grafana-pyroscope-datasource'
        tags: [{ key: 'job' }, { key: 'instance' }, { key: 'pod' }, { key: 'namespace' }]
        profileTypeId: 'process_cpu:cpu:nanoseconds:cpu:nanoseconds'
        customQuery: true
        query: 'method="$${__span.tags.method}"'
      serviceMap:
        datasourceUid: 'prometheus'
      nodeGraph:
        enabled: true
      search:
        hide: false
      traceQuery:
        timeShiftEnabled: true
        spanStartTimeShift: '-1h'
        spanEndTimeShift: '1h'
      spanBar:
        type: 'Tag'
        tag: 'http.path'
      streamingEnabled:
        search: true
        metrics: true
```

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

### Example HTTP Request with X-Grafana-Org-Id

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api

This example demonstrates how to include the X-Grafana-Org-Id header in an HTTP GET request to specify the target organization.

```http
GET /api/org/ HTTP/1.1
Accept: application/json
Content-Type: application/json
X-Grafana-Org-Id: 2
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
```

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

### Start Grafana Server on Windows

Source: https://grafana.com/docs/grafana/latest/installation/restart-grafana

Execute this command in the bin directory to start the Grafana server on Windows.

```bash
grafana.exe server
```

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

### Get Current Organization Response

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/api-legacy/org

Example response for the 'Get Current Organization' endpoint, showing the organization's ID and name.

```http
HTTP/1.1 200
Content-Type: application/json

{
  "id":1,
  "name":"Main Org."
}
```

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

### Example Response for Create Folder

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/folder

Shows a successful response after creating a folder, detailing its generated metadata and specifications.

```json
HTTP/1.1 200
Content-Type: application/json
{
  "kind": "Folder",
  "apiVersion": "folder.grafana.app/v1",
  "metadata": {
    "name": "eef33r1fprd34d",
    "namespace": "default",
    "uid": "X8momvVZnsXdOqvLD9I4ngqLVif2CgRWXHy9xb2UgjQX",
    "resourceVersion": "1741320415009",
    "creationTimestamp": "2025-03-07T04:06:55Z",
    "labels": {
      "grafana.app/deprecatedInternalID": "1159"
    },
    "annotations": {
      "grafana.app/folder": "fef30w4jaxla8b",
      "grafana.app/createdBy": "service-account:cef2t2rfm73lsb"
    }
  },
  "spec": {
    "title": "child-folder"
  }
}
```

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

### Get Single User by ID Response Example

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/api-legacy/user

Example response for retrieving a single user by ID, containing detailed user information.

```json
HTTP/1.1 200
Content-Type: application/json

{
  "id": "1",
  "email": "user@mygraf.com",
  "name": "admin",
  "login": "admin",
  "theme": "light",
  "orgId": 1,
  "isGrafanaAdmin": true,
  "isDisabled": true,
  "isExternal": false,
  "authLabels": [],
  "updatedAt": "2019-09-09T11:31:26+01:00",
  "createdAt": "2019-09-09T11:31:26+01:00",
  "avatarUrl": ""
}
```

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

### Configure Email Welcome and Templates

Source: https://grafana.com/docs/grafana/latest/administration/configuration

Configure welcome email on sign-up and email template patterns. Default template pattern is `emails/*.html, emails/*.txt`.

```ini
[emails]
welcome_email_on_sign_up = true
templates_pattern = "custom_emails/*.html, custom_emails/*.txt"
```

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

### Example Folder Structure for Permissions

Source: https://grafana.com/docs/grafana/latest/administration/roles-and-permissions/folder-access-control

This example illustrates a recommended folder structure for managing team-specific access and shared content. It shows how top-level folders can be assigned to teams, with subfolders inheriting permissions, and shared folders allowing for controlled cross-team visibility.

```none
SRE Team/                      # SRE team has Admin
├── Production Monitoring/     # Inherited Admin
├── On-Call Dashboards/        # Inherited Admin
└── Runbooks/                  # Inherited Admin

Platform Team/                 # Platform team has Admin
├── Infrastructure/            # Inherited Admin
└── Cost Tracking/             # Inherited Admin

Shared/                        # Everyone has View, specific teams have Edit
├── Company KPIs/              # Marketing team has Edit
└── Executive Dashboards/      # Leadership has View
```

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

### Template Output Example

Source: https://grafana.com/docs/grafana/latest/alerting/configure-notifications/template-notifications/reference

This shows the expected output from the 'custom_template' Go template when processed. It displays the start time with timezone information and a formatted start time.

```template-output
2024-10-30 21:01:45.227 +0100 CET
21:01:45 CET

```

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

### Setting a Semi-Relative Time Range (Example 2)

Source: https://grafana.com/docs/grafana/latest/dashboards/time-range-controls

Configure a semi-relative time range to track progress within business hours. This example sets the start time to 8 AM today and the end time to 'now', effectively monitoring the current day's progress from a specific start hour.

```text
Start time: now/d+8h

End time: now
```

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

### Example configuration settings

Source: https://grafana.com/docs/grafana/latest/administration/configuration

This INI block shows sample configuration settings across different sections, including default, security, auth.google, plugin.grafana-image-renderer, and feature_toggles.

```ini
# default section
instance_name = ${HOSTNAME}

[security]
admin_user = admin

[auth.google]
client_secret = 0ldS3cretKey

[plugin.grafana-image-renderer]
rendering_ignore_https_errors = true

[feature_toggles]
newNavigation = true
```

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

### Enable Grafana Server to Start at Boot with systemd

Source: https://grafana.com/docs/grafana/latest/installation/restart-grafana

Configure the Grafana server to automatically start when the system boots up using systemd.

```bash
sudo systemctl enable grafana-server.service
```

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

### Example Response for Plugin Installation

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/cloud-api

This JSON object represents a successful response after installing or updating a plugin in Grafana Cloud. It includes details about the plugin, its version, and associated instance information.

```json
{
  "id": 256519,
  "instanceId": 507363,
  "instanceUrl": "https://createcloudstack.grafana.net",
  "instanceSlug": "createcloudstack",
  "pluginId": 663,
  "pluginSlug": "grafana-github-datasource",
  "pluginName": "GitHub",
  "version": "1.3.0",
  "latestVersion": "1.3.1",
  "createdAt": "2023-01-04T08:50:42.000Z",
  "updatedAt": "2023-01-04T08:55:00.088Z",
  "links": [
    {
      "rel": "self",
      "href": "/instances/createcloudstack/plugins/grafana-github-datasource"
    },
    {
      "rel": "instance",
      "href": "/instances/createcloudstack"
    }
  ]
}
```

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

### Example Rules for Team A (Multiple Selectors)

Source: https://grafana.com/docs/grafana/latest/administration/data-source-management/teamlbac/create-teamlbac-rules

Grants access to logs in 'us-west-0' cluster with 'dev' or 'prod' namespaces.

```logql
cluster="us-west-0", namespace=~"dev|prod"
```

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

### Start Grafana Server with init.d

Source: https://grafana.com/docs/grafana/latest/installation/restart-grafana

Use these commands to start the Grafana server service and check its status when using init.d.

```bash
sudo service grafana-server start
```

```bash
sudo service grafana-server status
```

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

### Get Team Members API Response

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/api-legacy/team

Example response containing a list of team members.

```json
[
  {
    "orgId": 1,
    "teamId": 1,
    "userId": 3,
    "email": "user1@email.com",
    "login": "user1",
    "avatarUrl": "\/avatar\/1b3c32f6386b0185c40d359cdc733a79"
  },
  {
    "orgId": 1,
    "teamId": 1,
    "userId": 2,
    "email": "user2@email.com",
    "login": "user2",
    "avatarUrl": "\/avatar\/cad3c68da76e45d10269e8ef02f8e73e"
  }
]
```

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

### Install gcx from Source using Go

Source: https://grafana.com/docs/grafana/latest/as-code/observability-as-code/grafana-cli/gcx/installation

Install gcx from source using the Go toolchain. Ensure you have git and Go 1.24 or later installed.

```shell
go install github.com/grafana/gcx/cmd/gcx@latest
```

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

### Get all mute timings

Source: https://grafana.com/docs/grafana/latest/alerting/set-up/provision-alerting-resources/http-api-provisioning

Retrieves all configured mute timings. Includes an example request and response.

```APIDOC
## GET /api/v1/provisioning/mute-timings

### Description
Get all the mute timings.

### Method
GET

### Endpoint
/api/v1/provisioning/mute-timings

### Request Example
```http
GET /api/v1/provisioning/mute-timings
Accept: application/json
Content-Type: application/json
Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
```

### Response
#### Success Response (200)
- **name** (string) - The name of the mute timing.
- **time_intervals** (array) - A list of time intervals for the mute timing.
  - **weekdays** (array) - Days of the week the mute timing applies to.
- **version** (string) - The version of the mute timing.
- **provenance** (string) - The source of the mute timing configuration.

#### Response Example
```json
[
  {
    "name": "weekends",
    "time_intervals": [
      {
        "weekdays": [
          "saturday",
          "sunday"
        ]
      }
    ],
    "version": "",
    "provenance": "file"
  }
]
```
```

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

### Get All Users in Current Organization Response

Source: https://grafana.com/docs/grafana/latest/developer-resources/api-reference/http-api/api-legacy/org

Example response for 'Get All Users in Current Organization', detailing each user's organization ID, user ID, email, role, and last seen information.

```http
HTTP/1.1 200
Content-Type: application/json

[
  {
    "orgId": 1,
    "userId": 1,
    "email": "admin@localhost",
    "avatarUrl": "/avatar/46d229b033af06a191ff2267bca9ae56",
    "login": "admin",
    "role": "Admin",
    "lastSeenAt": "2019-08-09T11:02:49+02:00",
    "lastSeenAtAge": "< 1m"
  }
]
```