Windows setup.exe

1. Installation

Download the latest setup.exe from https://github.com/Krillsson/monitee-agent/releases/latest and run it

Files will be installed to C:/Program Files/sysapi/

Leave Install and start sysapi as a Windows service checked to have setup register the service and start it when it finishes.

2. Configuration

Use your favorite text editor to edit the user & password of the configuration.yml inside the config directory C:/Program Files/sysapi/config/configuration.yml

user: 
  username: user # <--- CHANGE ME
  password: password  # <--- AND ME

If you need to change the default application ports 8080 and 8443, you can do so in the C:/Program Files/sysapi/config/application.properties file

Restart the sys-api service in the Services program for the changes to take effect.

CPU temperature, fan and voltage show up when LibreHardwareMonitor 0.9.4 or OpenHardwareMonitor is running next to the agent. Later LibreHardwareMonitor versions no longer publish the WMI data the agent reads.

The agent runs the native build, which uses less memory, and falls back to Java on hosts it can’t run on. To choose for yourself, put the word in a file named runtime in the config directory and restart the service: jvm always runs Java, native runs the native build without falling back, and auto is the default. From an administrator Command Prompt:

echo jvm> "C:\Program Files\sysapi\config\runtime"

3. Checking that it runs

The service writes its output to sys-API-servicew.out.log in the installation directory.

When you see:

[...]: Tomcat started on ports 8443 (https), 8080 (http) with context path '/'
[...]: Started SysAPIApplicationKt in 6.352 seconds (process running for 7.234)

We know that the server is up

If you chose not to install the service, you can run sysapi.exe directly instead. A console window will pop-up and show the same output.

The service can also be managed with the install-service.bat, start-service.bat, stop-service.bat and uninstall-service.bat files in the installation directory. They are just calling sys-API-servicew.exe with different arguments. You can take a look at winsw documentation if you want to learn more.

4. Upgrading

Run the setup.exe of the newer version. It stops the service, replaces the files and starts the service again. Your config directory is left as it is.

Now you are ready to proceed to next step

Connect App to Server