HFS Monitor for Windows

[pavelnil]

Feedback and sharing are welcome!

HFS Monitor Windows WPF application on .NET 6.

HFS Monitor is a monitoring tool for HTTP File Server version 3 (HFS 3), providing detailed real-time network activity analytics. The application displays traffic graphs, active connections, and current data transfer speeds. Portable version requiring no installation. All settings are stored in a file. Inherits certain principles from the HFS 2.3 ideology.

---

hfs-monitor-agent

hfs-monitor-agent is a plugin developed for HTTP File Server version 3 (HFS 3), providing essential tools and data for integration with the HFS Monitor application.

[rejetto]

congratulations for your project :)
why didn't you rely on the same APIs used by the admin-panel? so to avoid the need of the plugin part

[pavelnil]

Thank You!
At the start, I didn't realize you could access /~/api/ directly. Later, when I saw it mentioned that the Admin Panel API isn't documented (with DevTools suggested instead), I assumed this wasn't the standard or recommended way. I didn't explore the Admin Panel's /~/api/ endpoints, thinking they offered fewer features.
The plugin got its own speed calculation and debug logging.
Later, a different calculation appeared in the frontend. I didn't check which one is more accurate to save time. I left it as-is for now.
I originally planned HTTPS and login for remote access. But I quickly found HTTPS would take much longer than expected and has many complications. Also, the need for remote HFS access wasn't clear.
I considered storing historical data for charts and connection stats in a database. It seemed logical to handle this in the plugin. But I worried it would be frustrating if HFS added similar features in its final 2025 release before I finished.
Why didn't I use the Admin Panel API? Mainly because of how things developed. Requirements changed as we went, and the effort/difficulty wasn't clear upfront.
From a "perfect solution" perspective, the plugin should probably be removed.
Maybe later the Monitor plugin will be needed for something the Admin Panel API can't do (file sizes).
If switching to the Admin Panel API makes sense, I don't think it would take much time.