Query Timeout

[Premkumar-Rasu]

Hi Team,

We are currently using the Dataset data source plugin in Grafana to integrate with Microsoft Sentinel. We’ve observed that when running Power Query-based queries, if the query takes longer to respond, no timeout is triggered, and the request continues indefinitely.

We would like to understand:

Is this expected behavior?
Are there any default timeout settings configured at the backend or code level for this plugin?

[weilliu]

@Premkumar-Rasu Could you send the question to our support portal https://support.dataset.com/hc/en-us

Please include the query used and the DataSet account information so we can investigate what happens to those requests. A screenshot showing that the query runs indefinitely will also be needed.

Did you try running the same query from the DataSet directly? Can you also send us a search link? No query should run perpetually without timeouts, so this is definitely an abnormal behavior

[Premkumar-Rasu]

@weilliu Dataset support ticket #10064

To confirm, all queries have been thoroughly tested against the dataset directly before being integrated into Grafana for visualization.

With the support of the our Sentinel team, we have now fine-tuned and prioritized these queries at the Sentinel backend. As a result, the response time has improved considerably and is now consistently under 30 seconds.

We would like to explore the possibility of configuring timeout settings at the Grafana level—specifically at the data source plugin UI level. This would help us better align with the varying refresh intervals across different dashboards.

For example:
Dashboards refreshing every 1 minute require query responses within 30 seconds.

Dashboards refreshing every hour or more can tolerate longer execution times without impacting usability.

We would also like to highlight that most data sources in Grafana typically offer timeout configuration options at the data source plugin level within the UI.

It would be helpful to understand:

Whether timeout setting is currently available in plugin backend code.
If not, is there any plan to expose this capability in the UI or backend configuration in the near future?

Thanks,
Premkumar R