RPi Temperature Status Test

Raspberry Pi is a pretty powerful device and low-end mobile computer. Raspberry Pi consumes very less power compare to your desktop CPU. But just like every other computer, while performing heavy tasks, it also gets hot. Since the device is small in size, it does not have fans to cool it down like other desktop/laptop CPU's, so it is configured to operate within a certain temperature range. The system on a chip (SoC) of the Raspberry Pi has a temperature sensor that can be used to measure its temperature. If your temperature rises above the configured value, you will see a little thermometer on you Raspbian desktop to indicate that your Pi is getting hot. As the core temperature rises, the thermometer gets to fill. Then at higher value, it changes to a full thermometer. If the temperature reaches the higher level, your CPU (ARM core) starts throttling and reduces the clock to cool down the temperature. This will decrease the performance. This is why, it is important for administrators to periodically check the temperature of the device. This can be easily done using the RPi Temperature Status test.

This test reports the core temperature of the device and proactively alerts administrators to an unusual spike/drop in the temperature of the device, and thus enables them to quickly bring the temperature under control before it causes irreparable damage.

Target of the test : A Raspberry Pi Device

Agent deploying the test : An external agent

Outputs of the test : One set of results for the Raspberry Pi device is being monitored.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed
Host	The IP address of the Raspberry Pi device that is being monitored.
Use Sudo	The eG agent runs native Linux commands to pull metrics from the Raspberry Pi system. By default, the eG agent does not require any special permissions to execute these commands. In some highly-secure Linux environments however, the eG agent install user may not have the permissions to execute these commands directly. To grant permission to eG agent install user for command execution, first, perform the following steps: Edit the SUDOERS file on the target host and append an entry of the following format to it: <eG_agent_install_user> ALL=(ALL) NOPASSWD For instance, if the eG agent install user is eguser, then the entry in the SUDOERS file should be: eguser ALL=(ALL) NOPASSWD Finally, save the file. Then, when configuring this test using the eG admin interface, set the USE SUDO parameter to Yes. This will enable the eG agent to execute the Linux commands and retrieve the metrics.
Sudo Path	This parameter is relevant only when the USE SUDO parameter is set to ‘Yes’. By default, the SUDO PATH is set to none. This implies that the sudo command is in its default location – i.e., in the /usr/bin or /usr/sbin folder of the target host. In this case, once the Use Sudo flag is set to Yes, the eG agent automatically runs the sudo command from its default location. However, if the sudo command is available in a different location in your environment, you will have to explicitly specify the full path to the sudo command in the Sudo Path text box.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Temperature	Indicates the core temperature of the device.	Celsius	An unusually high or low value for this measure is a cause for concern as it could indicate a potential hardware failure.