When you connect Grafana to the Tempo-compatible API provided by Application Real-Time Monitoring Service (ARMS), you may encounter connection, authentication, or configuration errors. This topic explains the root cause of each error and provides step-by-step solutions.
Error summary
The following table lists the errors covered in this topic. Click an error to jump to its solution.
| Error type | Error message | Typical cause |
|---|---|---|
| Connection | Unable to connect with Tempo | Malformed or unsupported endpoint URL |
| Authentication | Authentication failed | Mismatched AccessKey ID and AccessKey secret |
| Configuration | Trace Logstore Not Found | Incorrect user ID or missing trace logstore |
Connection error: incorrect endpoint URL
Error message
Unable to connect with Tempo. Please check the server logs for more details.Cause
The Tempo data source URL in Grafana is malformed, or the specified region does not support the Tempo-compatible API.
Solution
Open your Grafana Tempo data source configuration.
Check the endpoint URL against the supported regions and endpoint formats.
Confirm that the region in the URL matches the region where your ARMS instance is deployed.
Save the data source configuration and click Test to verify the connection.
Tip: A common mistake is omitting the protocol prefix or using an incorrect region identifier in the endpoint URL. Double-check both before retesting.
Authentication error: mismatched credentials
Error message
Unable to connect with Tempo ([Authentication failed] The userId in HTTP header does not match the credentials (username/password). TraceId=xxxx). Please check the server logs for more details.Cause
The AccessKey ID and AccessKey secret do not match, or the AccessKey ID lacks the permissions required to access the Tempo-compatible API.
Solution
Verify the username and password in the Grafana Tempo data source configuration:
Username: Your AccessKey ID.
Password: Your AccessKey secret.
Confirm that the AccessKey pair belongs to the correct Alibaba Cloud account.
If the credentials are correct but the error persists, confirm that the AccessKey ID has been granted the required permissions for the Tempo-compatible API.
Tip: If you recently rotated your AccessKey pair, update both the AccessKey ID and AccessKey secret in Grafana.
Configuration error: trace logstore not found
Error message
Unable to connect with Tempo ([Trace Logstore Not Found] Please verify the UserId and RegionId in HTTP headers are correct, and ensure the trace logstore exists. TraceId=xxxxx). Please check the server logs for more details.Cause
The user ID in the HTTP header does not match an Alibaba Cloud account with an active trace logstore, or the RegionId points to a region where no trace logstore exists.
Solution
Verify that the user ID in the HTTP header corresponds to the Alibaba Cloud account that owns the ARMS instance and trace logstore.
Confirm that a trace logstore exists in the region specified by the RegionId header. If no trace logstore exists, set up trace data collection in the ARMS console first.
If you use a RAM user, verify that the RAM user belongs to the correct Alibaba Cloud account and has access to the ARMS resources.
Diagnostic checklist
If the solutions above do not resolve your issue, work through the following checklist:
| Check | Action |
|---|---|
| Endpoint format | Verify the URL starts with https:// and uses the correct region identifier. See supported endpoints. |
| Credential validity | Confirm the AccessKey ID and AccessKey secret are active and not expired or revoked. |
| Permission scope | Confirm the AccessKey ID has the required ARMS permissions for the Tempo-compatible API. |
| Region alignment | Confirm the region in the endpoint URL matches the region of your ARMS instance and trace logstore. |
| Network connectivity | Verify that firewalls, security groups, or proxy settings do not block the connection between Grafana and the ARMS endpoint. |
| Grafana server logs | Check the Grafana server logs for additional error details beyond the UI error message. |
Contact support
If none of the above steps resolve the issue, contact Alibaba Cloud technical support with the following information:
The TraceId from the error message
The endpoint URL you configured (with credentials removed)
The Grafana version and Tempo data source plugin version