To monitor an endpoint, you need an Observer. As a SaaS customer you can use Observers already provided by us. We offer an observer located in Frankfurt am Main and in East Virginia (USA).

Keep the Observer software component up to date and perform updates regularly.

Permanent monitoring of the Observer can only be ensured if the IP addresses from which monitoring is performed are not blocked by firewall rules. If necessary, unblock the following IP addresses when using the observers available on the SaaS platform:

Optionally allow all A-records from this domain:

Add Observer

If you are a SaaS customer and want to add additional locations, eg. to provide access to endpoints on the intranet, you can do so in any number. As an On-Premises customer, you must always install an Observer to monitor endpoints. To do this, you need a Linux-powered server (Debian, CentOS). Of course you can also work with a virtual machine.

  1. Go to Endpoints → Observers→ Add Observer

  2. Run the installation script with root-privileges on the desired Linux device.

The Observer automatically connects to the Enginsight platform.

Configure Observer

After the installation you have to configure your Observer. For this, simply click on the Observer you have installed.

  1. Assign an 'Alias' to give your Observer a unique name.

  2. Specify how many endpoints the observer should process in parallel. The correct setting depends on the performance you are providing to the Observer. By default, we choose 2. Adjust this setting if necessary.

  3. Define the region to which the observer should be assigned (e.g. London, server room...).

  4. Switch on the desired functions. The correct setting depends on the performance you provide to the Observer. As default setting we choose 2. Adjust this setting if necessary.

If you assign several observers to the same region, they will automatically share the monitoring of the endpoints.


If you are operating Enginsight as your own on-premises instance, you have two additional options.

  1. Dedicated Observer: Specify whether you want to use the Observer as an organization's dedicated Observer, or whether you want the Observer to be shared with all organizations.

  2. Internal targets: Restrict the observer's access targets. The observer only has the rights to access internal IP addresses if the "Internal targets" option is enabled. This option is important if you are not using the Observer as a dedicated observer, so that other organizations cannot monitor internal IP addresses.

Update Observer

The Enginsight Observer is continuously updated by us. In order for all (new) functions to work as desired, it is necessary that you always keep the watchdog up to date.

  1. Go to Enpoints → Observers and check if all version numbers are up to date. A warning will be given to you if an outdated version is installed.

  2. If an Observer does not have the current version number, click the Update button in the right column at Actions.

The current version number can always be found here.

Get logs

To check the current logs of the Observer software component, you have two options.

User interface: Logs button

Click the 'Logs' button at Endpoints → Observers.

After clicking the Logs button, the current logs will be pulled. The transfer is limited to 2MB.

How far back the logs go also depends on the configuration and the load of the server.

On the Observer server: Get and save logs

If you have access to the Observer server, you can also read out the current logs directly. The best way is to save the logs into a .txt-file.

Use the commands below to do this. Adjust the file name before you do this.


cat /var/log/syslog | grep -a observer-m9 > /tmp/<filename>.txt


cat /var/log/messages | grep -a observer-m9 > /tmp/<filename>.txt

How far back in time the logs go depends on the configuration and load of the server.

Last updated