# Best Practices with Grafana as frontend for Dashboarding and Reporting Displays **URL:** \ **Category:** General Discussion\ **Tags:** perspective\ **Created:** [October 23, 2026, 3:23pm UTC](https://forum.inductiveautomation.com/t/best-practices-with-grafana-as-frontend-for-dashboarding-and-reporting-displays/117591 "2026-10-23T15:23:14Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Charles2044](https://avatars.discourse-cdn.com/v4/letter/c/b19c9b/32.png) [@Charles2044](https://forum.inductiveautomation.com/u/Charles2044)\ **Post date:** [October 23, 2026, 3:23pm UTC](https://forum.inductiveautomation.com/t/best-practices-with-grafana-as-frontend-for-dashboarding-and-reporting-displays/117591/1 "2026-10-23T15:23:14Z")
Grafana is the preferred display for management. Are there any recommendations for best practices or Design paradigms to follow? We created a webdev endpoint in 8.1.x to provide historical data to Grafana, and this has been working fine for the last few years. There have been some questions regarding our direction (performance wise), so I am looking for guidance from the forum. Where are the bottlenecks? Queries per second? bytes requested per second? for network throughout? Is this basically what can the server handle? The Grafana displays ~3k were developed with a different historian /platform and we would like to move all these to Ignition one day. Note I am a Perspective fan, please don't respond that the best design paradigm is to move to perspective. ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [October 23, 2026, 5:57pm UTC](https://forum.inductiveautomation.com/t/best-practices-with-grafana-as-frontend-for-dashboarding-and-reporting-displays/117591/2 "2026-10-23T17:57:03Z")
In the past, I connected Grafana directly to the SQL Historian DB, and issue the same queries that Ignition was using to return data (there are a series of queries that Ignition issues to a database, in succession, in order to return the data from the appropriate tag ids within the various data tables). I can't recall specifics - but believe I created a view which made the (parameterized) query 'easy' from clients which connected to the Historian DB directly. This approach should increase your performance _significantly_ - at the expense of potential ongoing maintenance of your queries (schema might change between Ignition versions, database technologies, etc.). ---
**Author:** ![Charles2044](https://avatars.discourse-cdn.com/v4/letter/c/b19c9b/32.png) [@Charles2044](https://forum.inductiveautomation.com/u/Charles2044)\ **Post date:** [October 26, 2026, 3:47pm UTC](https://forum.inductiveautomation.com/t/best-practices-with-grafana-as-frontend-for-dashboarding-and-reporting-displays/117591/3 "2026-10-26T15:47:28Z")
Thank you for sharing this. It certainly is an avenue to explore.