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

# Grafana Loki

> Connect Grafana Loki and review log evidence in support investigations.

Connect Grafana Loki to let Decimal search application logs during support investigations.

## Before you connect

You'll need an organization admin account in Decimal and these connection details from your Loki administrator:

* **Loki URL:** the public HTTPS API base URL, reachable from Decimal. Use the Loki endpoint rather than your Grafana dashboard or a full ingestion or query URL.
* **User:** the user accepted by the endpoint's HTTP Basic authentication. For Grafana Cloud, use the log tenant ID for the intended stack.
* **Access token:** the token for that user with permission to read the relevant logs. For Grafana Cloud, use a Cloud Access Policy token with `logs:read` access to the stack.

Use credentials restricted to the logs this Decimal organization should read. Grafana's [token guide](https://grafana.com/docs/grafana-cloud/platform/security-and-account-management/security-and-access/authentication-and-permissions/access-policies/using-an-access-policy-token/) explains the tenant ID and token mapping.

## Connect Loki

1. Open **Settings → Integrations → Grafana Loki** in Decimal.
2. In **Connection**, enter the **Loki URL**, **User**, and **Access token**. All three fields are required.
3. Click **Connect**. Decimal checks the credentials and access to Loki's labels before saving the connection.
4. Check that **Status** reads **Connected** and that **URL** matches your intended endpoint.

## Review log results

Open an existing [ticket investigation](https://docs.decimal.app/support/ticket.md) and expand its log result. In **Query details**, check the time range and filters. Use **Show … more** to reveal additional entries already returned; it does not fetch another page. Displayed log times use your browser's local timezone.

Read the messages as well as the error count. That count is based on severity and message text, so it is a cue for review rather than a diagnosis. Loki results do not include an Explorer link; compare them with the appropriate data source in Grafana using the same time window.

**Limit reached** means older matches may be missing. Narrow the time window or filters, and check that the logs you need are within your Loki retention period.

## Troubleshoot the connection

| What you see | What to check |
| - | - |
| **Connect** is unavailable | Fill in all three connection fields. |
| An authentication error | Check the user, intended tenant, token expiry or revocation, and log-read permission. For Grafana Cloud, use the log tenant ID rather than your email address. |
| A URL or connection error | Check the public HTTPS Loki API base URL. Ask your administrator to confirm endpoint availability, DNS, TLS, and reachability from Decimal. |
| A missing stream-label error | Include a label and value returned by discovery. A request ID alone does not select a log stream. |
| **No logs found** | Compare the tenant, time range, retention, and label values with Grafana. Text searches are case-sensitive; multiple filters must all match. If an ID is stored only in structured metadata, ask to filter that field instead of the message. |
| An invalid time-range error | Use ISO 8601 timestamps with an explicit timezone, and put the start before the end. Check that the logs are still within your Loki retention period. |
| Searches stopped working | Check token validity, permissions, and Loki service health. A saved connection does not continuously recheck access. |

If the problem persists after these checks, [email support](mailto:support@getdecimal.ai) with the error, time range, non-sensitive filter details, and conversation or ticket URL. Leave tokens and sensitive log content out of the message.

## Replace tokens or disconnect

Prepare replacement credentials before disconnecting. On the Loki integration page, click **Disconnect** and confirm, then enter the replacement values and click **Connect**. Coordinate the interruption with your team. After reconnecting, confirm that **Status** is **Connected** and **URL** is correct.

Disconnecting removes Loki access from Decimal. To revoke the token itself, use Grafana or your authentication provider.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.