Getting I/o timeout error reading buckets

Question

I'm getting i/o timeout error reading buckets when selecting influx DB as DataSource in managed Grafana.

Also I read this doc(https://learn.microsoft.com/en-us/azure/managed-grafana/how-to-connect-to-data-source-privately), and created Managed private endpoint in Azure Managed Grafana and hooked up with private link service for influx DB VM and approved Grafana endpoint under private link service connections.

Below are the details I used for authentication when adding DataSource in Grafana
Query language: Flux

HTTP
**URL: http://

Answer 1

Hi @Satya
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here. 

First check that both Grafana and InfluxDB are on the same Virtual Network (VNet) or successfully connected through VNet Peering. If they are on different networks, they cannot communicate, which can cause time delays. 

Next because you are using a private IP, it is important that Grafana can configure the private IP of your InfluxDB instance. To resolve InfluxDB’s private IP address, make sure your DNS settings in Azure are configured correctly so that Grafana can access it. 

Verify that the URL you entered for your InfluxDB data source in Grafana is correct. It should use the private IP of the InfluxDB VM and do something like this: http://<private_ip_of_influxdb>:8086 Make sure you don’t use public URLs — since you’re connecting through a private endpoint, Grafana needs an internal IP. 

Also, check firewall and Network Security Group (NSG) configuration on both Grafana instances and InfluxDB VMs. Verify that port 8086 is open and allows traffic between the two systems. 

For additional trouble, you can use the curl command to test the connection from another machine on the same network. For example, you can run:  curl http://:8086/query?q=SHOW+DATABASES 

This will confirm if you can access the InfluxDB instance through a private network. If this test fails, there may be a problem with the network or firewall configuration. 

You can also try increasing the system cut-off time in Grafana if the error is related to long-running queries. You can find this option in the Data Sources section under your InfluxDB configuration. 

Finally, if none of this works, looking at the Grafana logs can give you more information about what could be causing the timeout. The logs can show specific errors that can help diagnose the problem.
If you have any further queries, do let us know  

---

If the answer is helpful, please click "Accept Answer" and "Upvote it"