> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fabricgateway.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fabricgateway.ai/_mcp/server.

# Sign in to fabric-observability

> Generate a one-time token in the console to sign in to your organization's fabric-observability app, and fix the errors that can stop it.

Some organizations keep their gateway telemetry in their own infrastructure and view it in the fabric-observability app instead of in the console. This topic shows you how to generate a token in the console that signs you in to that app.

## About fabric-observability

fabric-observability is the app that shows traces, logs, metrics, and AI spend for organizations that store telemetry on their own data plane. The console labels it **Fabric analytics**. When your organization uses it, the console doesn't show trace tables. **Traces** is named **Traces & Analytics**, **Analytics** is hidden, and the page shows a card instead.

To sign in, you don't use your console password. The console asks the control plane for a token, and the control plane has your data plane store a session for it. The data plane keeps the session in its coordination Redis. You paste the token into the app.

A token has the following properties:

* It starts with `fobs_`.
* It's shown once. The console doesn't store it, so generate another token if you lose it.
* It expires 30 minutes after you generate it if you don't use it. The app extends the session while you're active.

## Prerequisites

Before you begin, make sure you have the following:

* An organization that views telemetry in the fabric-observability app.
* A data plane that's running and [connected to the control plane](/run/connect-a-data-plane), on a version that supports sign-in tokens.
* To generate a token for the whole organization, the organization admin role, with permission to view traces. To generate a token for one namespace, permission to view traces in that namespace.
* A signed-in console session. An API key can't generate a token, and the request fails with `a signed-in user session is required`.

## Generate a token

To generate a token for your organization, do the following:

1. In the sidebar, select **Admin** and then **Traces & Analytics**.
2. Select **Generate sign-in token**. If you don't have permission, the button doesn't appear, and the page tells you to contact an organization admin.
3. In the **Fabric analytics sign-in token** dialog, check the **Organization** shown.
4. Select the copy button next to **Sign-in token**.
5. To open the app, select **Open Fabric analytics**. Otherwise, select **Close**.
6. In the app, paste the token to sign in.

The **Open Fabric analytics** button appears only after an admin sets **Fabric analytics URL** on the **General** page.

To generate a token for one namespace, select **Traces & Analytics** in that namespace's sidebar and select **Generate sign-in token**. The dialog shows a **Namespace** row. The token signs in to that namespace only, with the viewer role, whatever your role in the organization.

## Fix errors

If the console can't generate a token, it shows a message in a notification.

| Message                                                                       | Code                                      | What it means and how to fix it                                                                                                                                                       |
| ----------------------------------------------------------------------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| This org views observability in Fabric, not the fabric-observability app.     | `observability_app_not_selected`          | Your organization isn't set to use the app, so use **Traces** in the console. To use the app, ask your administrator to change the setting.                                           |
| Your data plane is not connected. Check that it is running and try again.     | `data_plane_not_connected`                | The control plane has no connection to your data plane. Check that the data plane is running and can reach the control plane. The console retries twice before it shows this message. |
| Your data plane did not respond in time. Try again.                           | `data_plane_timeout`                      | The data plane didn't confirm the session in time. Try again. If it keeps happening, check the data plane's load and its connection to Redis.                                         |
| Your data plane is too old to issue sign-in tokens. Upgrade it and try again. | `data_plane_upgrade_required`             | The data plane version doesn't support sign-in tokens. [Upgrade it](/run/upgrade).                                                                                                    |
| Could not generate a sign-in token. Try again.                                | `data_plane_store_error` and other errors | The data plane couldn't store the session, which usually means a problem with its coordination Redis. Check that Redis is reachable from the data plane, and try again.               |

## Next steps

* To use the console's trace view instead, see [Inspect traces](/use/monitor/traces).
* To review trends in the console, see [Review analytics](/use/monitor/analytics).