Skip to content


The menu section Settings in the Watcher web interface allows the Watcher administrator to edit the following settings of Flussonic Watcher:

General Watcher settings

Common settings

  • Mode – is displayed if Watcher works in multi-server mode (Cluster). If Watcher works in single-server mode, DVR path is diplayed here instead of Mode.

    Watcher modes are descibed in Installing Watcher

  • DVR path — the path to the DVR archive storage. It can be a Swift storage, not only a local storage. This setting is displayed only in single-server mode. In cluster mode, the DVR path must be configured for each streamer in the streamer settings on the managing server (see Streamers below).

    Watcher modes are descibed in Installing Watcher

  • Streamers - the link to the page for managing streamers. It becomes active in cluster mode.

  • API key — a token used for mobile access. You need to use it in your Account on the Flussonic website to activate access to mobile applications.

  • Language — the default UI language. If no default language is selected, Watcher will use the same language that is used by the browser.

  • GA key — your Google Analytics key for Watcher. With Google Analytics you can gather statistics on Watcher usage by users.

  • Guest access – allows users to access Watrcher UI by a link to a UI page, without logging in. A guest has access to public cameras and the map.

  • Demo access — allows access in demonstration mode, by the link Demo access on the login page. Actions such as modifying Watcher settings are not availabe in this mode. You cannot change the password for the user Demo.

  • Cameras serial number management – turns on the management of camera serial numbers in Flussonic Watcher. It is necessary when you use the Flussonic Agent software on cameras.


  • Show map in main menu — show or hide the Map section from the main menu. The map is turned on by default.

  • Map center — geographic coordinates for map centering.

  • Map provider — select the map provider: Google, Openstreetmaps or OpenStreetMaps Offline.

  • Map key — the token of the geo cover in use (Google API key), allows automatically translate an address into coordinates in order to show the camera on the map.

Main page

  • Registration allowed — turns on the self-registration option.

  • Homepage — specifies what users will see upon login: map or dashboard.

  • Guest homepage — specifies what guests will see on the home page: map or dashboard.

  • External authentication – specify the HTTP address or address of RADIUS server that you use to authenticate users.


  • Operator ID — necessary for the Watcher mobile app. It is the ID of your Watcher, which is used in mobile apps to connect to a specific Watcher server.

Subscribers must enter this ID in their app to get access to their cameras. However, if an app was branded, it is enough to enter a login and password (because branded apps can only work with a specific Watcher server).

Event notification settings

You can select which events received from cameras Watcher will to process. Also, you can instruct Watcher to receive events sent from external systems. Motion detection events and license plate recognition events are supported. (Usage examples will be added here soon.)

  • External event notification URL — Watcher will send HTTP events to external sources specified here.

  • External event filter URL — the URL of your custom event handler. Watcher automatically sends the events received from cameras to this URL at the moment when an event takes place. Your script then receives an event from Watcher and returns (or doesn't return) the event ID. If the ID is returned, the event is considered confirmed and Watcher registers it in its database. Also, an email notification and push notification to the mobile application are sent. The archive interval around the event ([event_utc-10, event.utc+30]) is protected from deletion.

    If the script returns no identifier, the event is considered unconfirmed and is not registered in Watcher.

    If this field is not filled, then all events are registered in the Watcher.

    To sum up, this script is for your custom filtering of events. You can save only those events that you are interested in.

    Watcher uses the JSON format to send info about events to your handler:

    { "event":"video_activity", "camera_id":"test1", "algorithm":"plate_detector", "activity_type":"enter", "number":"ABCDEHKMOTX", "area_id": "0", "start_at": 1554883886, "end_at": 1554883886 } Example of the Simple Event collector.

  • Disable push notifications — notifications about video analytics events (such as motion events) will not be sent to the Watcher mobile app. This option is independent from your custom backend scripts.

Adding and configuring streamers in the UI

Before you add streamers to Watcher, you need to prepare them. Details

To add streamer servers to Watcher, go to Settings and click the link Streamers. This link is active only in cluster mode:

Streamer settings

By default, the local streamer is added to Watcher.

Streamer settings

To add a remote streamer, click the Create a streamer button and specify its settings.

API URL - this url is used for internal communication between the Watcher server and the streamer. It shall conform to the specifications of the FQDN.

Public URL - used to connect with streams at the streamer. It shall conform to the specifications of the FQDN.

Cluster key – the cluster key used in the cluster (the cluster_key option in the configuration file). If the streamer’s and Watcher's cluster keys are identical, there is no need to fill this field.

DVR path – the path to the archive. This field is required for the archive to be recorded. For example: /dvr or @my_raid for Flussonic RAID.

Streamer settings

The streamer appears in the list where you can edit its settings.

Streamer settings

When you have added a number of streamers, you must select the default one. Click the streamer in the list and then click Default. All new cameras will be added to the default stream server.

  • In the UI section Streamers you don’t need to add the host where Flussonic Watcher itself is deployed.
  • On all servers in a cluster identical date and time must be set.

For each streamer, you can enable the automatic use of redundant (backup) servers for streams ingest in case this streamer fails (see Failover).

Watcher UI branding settings

Learn more in Interface branding