Articles in this section

Events

Agents keep records of ongoing events in course of syncing and store them in storage folder in 'events' subdirectory. Events log schema is described here. These are uploaded to Management Console in real time and show up there on the following tabs:

- Events main tab
- Agents main tab
- Job run 
- An agent in a job run

Management Console only receives those events that are permitted by parameter events log filters in Agent profile. They remain in the events list in Console's UI even though the error or misconfiguration itself might have already been fixed. Starting with Resilio Connect v2.9 'warning' type of event is deprecated, and 'error' type is used instead. 

In a job run in Agent's details, there's option to fetch all the events, regardless of the configured filter of the events. 

events_on_demand.png

Management Console shows events in pages. Note, that only 5 pages are cached when browsing through events pages.

All events that agents send to MC are stored locally on Management Console server in its storage folder in data\reporting\files (2.9.1 and newer) and data\reporting\daily subdirectories. These are sqlite database .db files with two timestamps in their name: start and end of a record. By default each .db file keeps record for a day, new .db is started next day, and is deleted 14 days later. Manually deleting a database file clears the events from Console's UI. It's configurable and can be changed by adding 'ttl' into 'reporting' section of MC configuration file. The value is in milliseconds, so 7 days = 604800000.

Need to manually enable in 2.9

Starting from 2.9 recording events in the events.log file is deprecated. If this file is required by business workflow, you need to enable it back manually. To do it, set the parameter useEventsServerEndpoint to true as well as ensure that events_server section contains the filename parameter specified: 
"events_server": {
    "protocol": "https",
    "host": "0.0.0.0",
    "port": "8445",
    "filename": "data/events.log"
},
"reporting": {
    "useEventsServerEndpoint": true,
    "default": {
        "db": {
            "type": "sqlite",
            "dir": "data/reporting/daily"
        },
        "ttl": 604800000
    }
}
Restart MC for changes to take effect.

2.png  

Event's Columns

  • Source can be Management Console itself or an Agent, depending on where the error appeared. Clicking on an agent name opens the agent's details view. 
  • Component can be "Global" or a specific job.
    Component "Global" means that the event affects the overall Agent's misconfiguration. For example, agent's listening port if busy by another progress.
    • If the error affects a job execution, corresponding job run name appears as Component.
    • Component can be empty for "Management Console" source. 

Most frequent Events error messages are explained here.

 

Related articles