Skip to main content
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 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 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

If the problem persists after these checks, email support 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.