Configuration of RPiTempStatusTest

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.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host for which the test is to be configured has to be specified.

• The USE SUDO parameter applies only to Linux and Solaris systems. By default, the USE SUDO parameter is set to No. This indicates that, by default, this test will report metrics by executing the df -Pk –l command on the Solaris host. However, in some highly secure environments, the eG agent install user may not have the permissions to execute this command directly. In such cases, do the following:

• 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: <Command>

  For instance, if the eG agent install user is eguser, then the entry in the SUDOERS file should be:

  eguser ALL=(ALL) NOPASSWD: df –Pk -l

• Finally, save the file.

• Then, when configuring the test using the eG admin interface, set the USE SUDO parameter to Yes. This will enable the eG agent to execute the sudo df –Pk –l command and retrieve the desired metrics.

• 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 Solaris host. In this case, the eG agent automatically runs the df -Pk –l command with sudo from its default location, once the USE SUDO flag is set to Yes. 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 to enable the eG agent to run the sudo command.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.