Using the 3 bar hamburger icon on each module (widget) on Linux Dash, you can drag and re-arrange them.

All of your changes are saved in LocalStorage, so your changes will be preserved permanently on that browser for convenience.

Each of the modules (widgets) on the Linux Dash screen can be:

• minimized to hide it
• expanded in one click to maximize it
• adjusted to a custom width

These UI features allow you to focus your usage of Linux Dash at any given point to highlight the modules important to you.

Linux Dash comes in well under 1MB of source code and only shows data when client browsers request it. Unlike server-side agent processes, Linux Dash does not gather or maintain historical data-sets, allowing its purpose and footprint to remain focused to a smaller surface area.

There are several minimal server-side implementations of Linux Dash provided off-the-shelf. You have your choice of Node.js, Python, Go, and PHP. Majority of the complexity behind Linux Dash is in how it gathers the system-level information, allowing the server-side implementations to be limited to a small router-like application.

This allows users of Linux Dash to not introduce technology stack changes for the sake of a simple monitoring tool. Want your favorite stack to be supported? Simply review the Architecture & Contributor's Guide sections bellow and submit a Pull Request.

Linux Dash provides many data-points and data visualizations in real-time. Using websockets (if supported) and on-demand per-module data refresh, the data you see is exactly what your system is reporting as of right now.

Please note that this is as much a feature as it is a limitation on the scope of Linux Dash. If you need historical data aggregation or a more heavyweight server monitoring tool for system analysis, please use one of the plethora of tools and services that do just that.