> ## Documentation Index
> Fetch the complete documentation index at: https://ryvn.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Observability

> Inspect managed Grafana and configure environment routing for published observability stacks

Open **Settings > Connections > Observability** to see managed Grafana and observability stacks published by blueprint installations.

## Managed Grafana

Ryvn provisions the managed Grafana connection from hub configuration. You do not need to add a Grafana API key on this page.

<Tabs>
  <Tab title="Dashboard">
    Use **Settings > Connections > Observability** to inspect managed Grafana and open it with **Open Grafana**.
  </Tab>

  <Tab title="CLI">
    List Grafana connections and inspect the managed connection:

    ```bash theme={null}
    ryvn get connection --type grafana
    ryvn describe connection ryvn-managed-grafana
    ```

    The description includes the URL, status, settings, and datasource state. Add `-o json` for structured output.
  </Tab>
</Tabs>

Check the connection status:

| Status | Meaning |
| - | - |
| Configured | The organization has a managed Grafana connection. Use **Open Grafana** to access it. |
| Awaiting setup | Grafana is enabled, but organization setup has not completed yet. |
| Disabled | Grafana is disabled for the hub. |

The page shows the Grafana organization, default role, reconciliation interval, and datasource state. Use **Refresh** to reload the current state. If setup remains pending or datasource checks fail, contact your hub administrator or [Ryvn support](/docs/support/contact-us).

## Published observability connections

Observability blueprint installations can publish connections to their telemetry backends. These appear on this page after the blueprint publishes them.

<Tabs>
  <Tab title="Dashboard">
    Open a published connection to inspect its details. Use the environment controls to associate the environments whose telemetry belongs to that stack. Where a telemetry backend uses a different environment label, configure the alias to match that label.
  </Tab>

  <Tab title="CLI">
    Use the published connection's name from `ryvn get connection --type grafana`. For example:

    ```bash theme={null}
    ryvn describe connection acme-observability
    ryvn create telemetry-source acme-observability \
      --environment production --alias app-telemetry
    ```

    To change an existing assignment's alias:

    ```bash theme={null}
    ryvn update telemetry-source acme-observability \
      --environment production --alias production-telemetry
    ```

    To remove the environment from the connection:

    ```bash theme={null}
    ryvn delete telemetry-source acme-observability --environment production
    ```

    Omitting `--alias` on creation defaults a new assignment to the connection name and preserves an existing assignment's alias.
  </Tab>
</Tabs>

Associating an environment permits it to send telemetry; workloads must select the assignment alias in their telemetry labels. Changing an alias does not rewrite workload labels. Update the telemetry configuration separately if the emitted labels need to change.

For deployment metrics and logs, continue with [metrics](/docs/observability/metrics) and [logs](/docs/observability/logs).