Looks like it's using this package here [1] to gather the information. It lists support for Linux, macOS, "partial Windows", FreeBSD, OpenBSD, NetBSD and SunOS.
There's a compatibility table for the data you can access on each system.
This is correct. I have it currently deployed on an Arch setup, but I've also tested it on other flavors of Linux.
Tried testing on Windows as well, which is when I came across the issues with compatibility. Technically, it should still work for most of the graphs. The library just doesn't reliably give proper values for I/O (disk and network). There is also an additional Windows edge case where it does not return proper CPU temp values on AMD Ryzen CPUs.
So it could still work, with the simple workaround of not displaying those graphs on Windows, but since Windows was not exactly my intended use case anyway, I didn't really address it with the intention of doing so if / when it was needed.
If anyone reading this is serious about deploying on Windows, let me know.
Very cool! I currently use https://github.com/netdata/netdata for my monitoring but I like how clean/easy this is.
Nice project!
What platforms does the backend run on? Linux only? Or BSDs as well?
Looks like it's using this package here [1] to gather the information. It lists support for Linux, macOS, "partial Windows", FreeBSD, OpenBSD, NetBSD and SunOS.
There's a compatibility table for the data you can access on each system.
[1] https://www.npmjs.com/package/systeminformation
This is correct. I have it currently deployed on an Arch setup, but I've also tested it on other flavors of Linux.
Tried testing on Windows as well, which is when I came across the issues with compatibility. Technically, it should still work for most of the graphs. The library just doesn't reliably give proper values for I/O (disk and network). There is also an additional Windows edge case where it does not return proper CPU temp values on AMD Ryzen CPUs.
So it could still work, with the simple workaround of not displaying those graphs on Windows, but since Windows was not exactly my intended use case anyway, I didn't really address it with the intention of doing so if / when it was needed.
If anyone reading this is serious about deploying on Windows, let me know.