pfSense

There is a reason we haven't done this already, it doesn't scale and is likely to cause problems.

Reading the states locks pf and can cause performance degradation when done repeatedly. The larger the state table, the bigger the performance hit. Not only would the widget consume resources with large numbers of states (even with limits) reading the states data repeatedly will have a noticeable impact on network throughput if someone is sitting at the dashboard.

We've been working to eliminate these kinds of reads where possible, and adding more is out of the question at this time.

Maybe it could be considered as an add-on package (with tons of warnings discouraging its use) but it's not viable as a part of the base system.

The only place it would make sense is when a system is vastly overpowered for the load it is handling (few states, low throughput, tons of CPU available).