Feature Idea / Discussion: Excluding loopback and cluster sync queries from Dashboard stats to get "realistic" metrics?
Hey everyone,
I’m currently running a Technitium DNS cluster and noticed a small issue with the Dashboard statistics. Because the cluster nodes constantly query each other for sync and health checks, and local services use the loopback address (127.0.0.1 / ::1), my Dashboard graphs are heavily distorted.
The internal automated traffic completely floods the total query count. This makes it really hard to see and analyze actual, realistic client traffic because the percentages and charts are skewed by the background noise.
I'm thinking about opening a Feature Request on GitHub for an option to exclude specific IPs/subnets (like loopback and other cluster nodes) from the Dashboard UI calculations—while keeping them in the raw logs for debugging, of course.
Before I do, I wanted to ask the community:
- Are you guys running into the same issue with your clusters or local setups?
- How do you currently handle this to get clean metrics? (Anyone using Grafana workarounds?)
- Do you think a native "Exclude IPs from Dashboard Stats" settings toggle would be a useful addition?
Would love to hear your thoughts or suggestions on this before pitching it to the devs!