Remote Access

With remote access, you can manage a Syslog Watcher Server from Syslog Watcher Manager on another computer. Remote users sign in with a username and password; each user’s role defines what they can view and change. To set up remote access, enable it on the server computer and add users. Then connect from Manager on the other computer.

Enable Remote Access

On the server computer, connect Manager to the local server, and then:

  1. In the Server section of the main toolbar, click Server Server → Server Configuration Server Configuration…​

  2. Select the Server page.

  3. Set Allow remote access to Yes.

  4. Check Port and Connection.

  5. Click Apply.

Server page of Server Configuration: Allow remote access set to Yes
Remote access settings on the Server page of Server Configuration

If no users exist yet, Manager warns and opens Remote Access Users. Add at least one user; without users, no one can sign in.

Allow remote access

Yes lets Manager connect from other computers.

Port

TCP port for Manager connections (1–65535).

Connection

Plain (unencrypted) or Secure (encrypted). The Protocol in Manager’s connection settings must match.

Certificate

Certificate for Secure (encrypted), selected by name from TLS Certificates. The button next to the field opens the TLS Certificates window.

Private key password

Password for an encrypted private key. When you select a certificate whose key password is stored as a secret string, the field is filled with that secret (%PWD_<certificate name>%).

Local IP address

Local address to listen on. 0.0.0.0 listens on all IPv4 addresses of the computer; ::0 on all IPv6 addresses.

Secure Connection

When you set Connection to Secure (encrypted) and no certificate is selected, Manager generates a self-signed certificate named remote_access and selects it. The certificate has this computer’s name as Common Name (CN), a 2048-bit key, and is valid for 3650 days (10 years). Its key password is stored as the secret PWD_remote_access.

To use your own certificate instead, import it in TLS Certificates and select it in Certificate.

Remote Access Users

In the Server section of the main toolbar, click Server Server → Remote Access Users…​ On the Server page of Server Configuration, Manage Remote Access Users…​ opens the same window.

Remote Access Users window: three users with their full names and roles
The Remote Access Users window

Users who cannot manage other users see Remote Access Users: Self Only with only their own account, which they can edit.

Add a User

  1. Click Create New.

  2. Fill in the user properties.

  3. Click Create.

The first user is prefilled as admin with full name Administrator and role Admin. Further users start with the role Observer.

Edit a User

Select the user and click Edit…​, change the properties, and click Apply.

The Username cannot be changed. You cannot change your own Role.

Delete a User

Select the user, click Delete, and confirm. You cannot delete your own account.

User Properties

Edit User window: Username (read-only)
The Edit User window
Username

Sign-in name used to connect. Required and unique; cannot be changed after the user is created.

Password

Password for the connection. Required.

Full name

Name shown in the users list. Required.

Role

Admin, Operator, or Observer (see Roles).

Roles

Roles apply to remote sessions only. Manager on the server computer is not limited by roles: what it can do depends on the permissions of the Windows account that runs Manager. To connect to the local server, Manager asks for administrator rights.

Role: Admin

Everything: users, licenses, collector configuration and start/stop, storage location and limits, server configuration, secrets, certificates, and all storage objects.

Role: Operator

Day-to-day work: features (including suspend and resume), originators, groups, parsers, view layouts and presets, filter lists, field dictionaries and collections, report templates, scheduled reports, severity and facility names, server configuration, and test emails and HTTP requests.

Can add secrets and certificates, but not delete them. Can view, but not change, the collector configuration, storage location and limits, and licenses. Cannot manage other users or start and stop the collector.

Role: Observer

Read-only: status, configuration, diagnostic records, and stored messages. Can change only their own account and their own view tabs. Cannot schedule reports or send tests.