Dynatrace Plugin fails with Dynatrace Platform Token configured

Grafana Configuration
1

  • What Grafana version and what operating system are you using? Using Grafana version V12.4.4 running on Linux

  • What are you trying to achieve? Configure the Dynatrace plug-in with a DT Platform token for Grail API use

  • How are you trying to achieve it? Following the documentation posted here: Configure the Dynatrace data source | Grafana Enterprise Plugins documentation

  • What happened? When I entered the Dynatrace API Token it saved & tested successfully, but when I added the Dynatrace Platform Token the save & tested resulted in the following error:

There was a problem with connecting to Dynatrace.

failed to execute Grail query: status code (404) HTTP 404 Not Found
failed to execute Grail query: status code (404) HTTP 404 Not Found

  • What did you expect to happen? Successfully saved & tested

  • Can you copy/paste the configuration(s) that you are having problems with? No, Dynatrace datasource

  • Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were. See error above

  • Did you follow any online instructions? Yes If so, what is the URL? Configure the Dynatrace data source | Grafana Enterprise Plugins documentation

2

It looks like you didn’t configure correct Dynatrace API type for your use case, so incorrect URL is generated and that responds with 404 response code.

Try to increase Grafana log level and check which URL is Grafana calling.

Another problem can be version: Dynatrace is a enterprise plugin, so do you have Grafana Enterprise with valid license?

3

@jangaraj Thanks for your quick response, I do suspect the Grail API is having an issue with the URL as in our enterprise we are leveraging ac Dynatrace ActiveGate endpoint to funnel all the DT API calls through. Interestingly enough though the Dynatrace API Token successfully connects via the same URL it’s only the Grail API check with the platform token that is failing with the 404 response code. Also yes we do have Grafana Enterprise with a vailid license.

4

Dynatrace ActiveGate , so doc is saying:

Raw URL - Use this option for Dynatrace instances that don’t fit into the SaaS or Managed Cluster categories, such as Environment ActiveGate.

  • URL - The full URL of your Dynatrace instance. For example: https://yfc55578.live.dynatrace.com

You have Enterprise license, so contact your Grafana support for proper support. They have good knowledge or they will be able to ask Dynatrace plugins developer directly about your issues.

5

Are you using Dynatrace SaaS or Managed. I assume you are on SaaS as you mentioned as Grail API.

404 error HTTP not found point to teh incorrect URL / ID which is unable to find the target URL. Please double-check.

6

Since the API token validates successfully but the Platform token fails only during the Grail query, I’d recommend temporarily increasing Grafana’s log level to debug and checking the exact URL being called for the Grail validation.
Comparing that URL with the one used for the successful API token request should help determine whether Grafana is generating an incorrect endpoint/path or whether the ActiveGate isn’t proxying Grail requests correctly.

7

I assume it is Dynatrace SaaS and no activegates comes in-between for this integration as one can integrate directly with Dyntrace SaaS from Grafana Enterprise.

8

If it does turn out to be a direct SaaS integration with no ActiveGate involved, that would rule out the proxy/routing layer as a variable and point back to how the Grail endpoint itself is being constructed. At that point, comparing the Grail request Grafana generates with a known working Grail API request would help confirm whether the plugin is targeting the expected endpoint.