System Stats / Management¶

Launch the DietPi-CloudShell control panel:
dietpi-cloudshell

CloudShell offers scenes with predefined display outputs resp. layouts.
Scenes are configured in the Scenes dialog within dietpi-cloudshell.

This feature will allow you to automatically power down the screen and disable DietPi-CloudShell processing during a specific time.
Please note this feature requires DietPi-CloudShell to be launched with dietpi-autostart, or run dietpi-cloudshell from the main screen (tty1).
If you make changes to DietPi-CloudShell over SSH, once saved, please reboot the system to ensure this feature becomes activated.

Power saving: Auto screen off

See http://www.waveshare.com/3.2inch-rpi-lcd-b.htm.
This is available for all Raspberry PI and Odroid versions. DietPi will automatically configure your system for the device.
Simply run dietpi-config -> Display Options then select waveshare32.
After a reboot, your waveshare32 will become active.

See https://www.hardkernel.com/shop/c1-3-2inch-tfttouchscreen-shield/.
This is available for all Odroid versions. DietPi will automatically configure your system for the device.
Simply run dietpi-config -> Display Options then select odroid-lcd35.
After a reboot, your Odroid 3.5 LCD will become active.

The display feature of CloudShell works generally with any LCD display or monitor with a resolution of at least 320x240.

The web interface of Linux Dash can be accessed via:

• URL = http://<your.IP>/linuxdash/app

The web interface of phpSysInfo can be accessed via:

• URL = http://<your.IP>/phpsysinfo

This is done via the file phpsysinfo.ini which is located in the phpSysInfo main directory (typical /var/www/phpsysinfo). An example file phpsysinfo.ini.new is present and gives inline information about all configuration options. Just walk through this file and discover all these bells an whistles.

The main features of RPi-Monitor are:

• Collecting, storing and presenting metrics
• It’s flexibly configurable
• It’s user extendable
• Metrics sharing can be done via JSON file or via SNMP
• Alert option

The web interface of RPi-Monitor can be accessed via:

• URL = http://<your.IP>:8888

The configuration is described there: https://xavierberger.github.io/RPi-Monitor-docs/20_index.html.

The web interface of Netdata can be accessed via:

• URL = http://<your.IP>:19999

Depending on your system, by default Netdata might be not accessible from remote browsers. If this is the case, open the configuration file
/etc/netdata/netdata.conf
and change the line
bind socket to IP = 127.0.0.1
to match either the local network IP or static public IP of your server depending on your needs.
Alternatively comment it e.g. if your server does not have a static public IP but you require remote access.

Note that having Netdata accessible to anyone gives potential attackers a bunch of useful information where to start hacking.
About how to limit access to Netdata, check as well: https://docs.netdata.cloud/web/server/.

The monitoring of a Pi-hole system via Netdata is described there: https://learn.netdata.cloud/guides/monitor/pi-hole-raspberry-pi.

The web interface of Webmin can be accessed via:

• URL = https://<your.IP>:10000
• Username = root
• Password = root password at time of installation (default: dietpi)

The Webmin system logging panel still depends on a classical file logger, like Rsyslog. However DietPi will not impose this logging overhead on systems by default. If you need to see system logs via the Webmin online panel, you can either configure a custom syslog daemon or install Rsyslog manually:
apt install rsyslog

DietPi comes with systemd and the related journald system logger, which can be accessed via the command journalctl.