I noticed an Ignition project I have is running 6-10 queries/second against a db on my gateway. I am fairly sure that these queries are running automatically and do not relate to any views or scripts I have on the project (Note this project does not have any gateway timer scripts either). I also believe that most of these queries are tag historian related. I am assuming these things because:
The queries run when the designer is closed and 0 web sockets are opened
My goal now is to figure out if these queries are necessary or not, for the queries/second do seem high. Is there a way for me to find exactly what calling these queries?
Those are historian queries supporting real-time trends. The ones with "LIMT 1" are testing for the presence of data within a timespan, and the ones without are actually retrieving the trend data. The "INSERT" at the bottom is a fresh data point being stored.
What do you mean by real-time trends? I have meters/sensors that Ignition collects data from real-time and stores in the historian if this counts. The thing I find strange is how the system is retrieving data from historian partition tables corresponding to Dec 2025, Jan 2026, and Feb 2026.
What kind of trends would it be looking for within this data?
What triggers this trend search? Is it that Ignition users/programmers can configured or a part of Ignitions backend for the historian?
History trends set up for realtime display typically default to refreshing every second. So produce repeating query loads. History trends with a historical (static) time frame query just once. If someone was running a realtime trend with a three-month span (unwise, but not forbidden), you'd see such a query pattern.
Consider logging the start/end timespans of your trend charts so you can locate who/where such long spans are being used.
(Ignition won't do historian queries without some programmer setting it up. Either for a power chart or for a history binding driving some other component.)
