Events
Overview
Agents record events related to the Jobs they're participating in. These events are stored in the storage folder\events directory and uploaded to the Management Console where they can be viewed and analyzed.
Note
- The Management Console receives events that are enabled in the Event filter parameter in the Agent profile, but it is possible to fetch all logs from an Agent. For details, see Tip: Fetch all event log entries.
- The Management Console stores the events data in
.dbSQLite database files instorage folder\data\reporting\filesandstorage folder\data\reporting\dailyfolders. There's a set of.dbfiles for each day whose name contains start and end timestamps in the Unix time format. By default, the data is stored for 14 days before it's removed. To change the default time period, addttlvalue to thereportingobject in the Management Console's configuration file. Thettlvalue is expressed in milliseconds, for example 604800000 is 7 days.
Access event logs
You can access event logs:
- In the Events view
- On the Agent's details page
- On the Job run's details page
- On the Agent's details page in a specific Job run
Events view
The Events view is a central location for browsing all log events.
To access Events, log in to the Management Console and select Events.
Agent's details page
To view Agent's events:
- Select Agents.
- Locate and click the Agent whose logs you want to view.
- Select LOGS.
Job run's details page
To view events related to a specific Job run.
- Select Jobs.
- On the JOB RUNS tab, locate and click the desired Job run.
- Select LOGS.
Agent's details page in a specific Job run
To view events related to a given Agent for a specific Job run:
- Select Jobs.
- On the JOB RUNS tab, locate and click the desired Job run.
- Select AGENTS.
- On the AGENTS tab, locate and click the Agent whose logs you want to view.
- Select LOGS.
Tip: Fetch all event log entries
The Management Console receives event that are enabled in the Event filter parameter in the Agent profile. To fetch all events related to specific Agent in a given Job run:Recording events in the events.log file
In Resilio Active Everywhere 2.9, recording events in the events.log file has been disabled by default. If this file is essential for your existing workflows, you need to enable it manually. To do it, set the useEventsServerEndpoint parameter to true and make sure that events_server section contains the filename parameter specified in the Management Console's configuration file. Restart the Management Console to apply changes.
"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
}
}
Events log information
- 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.
Tip
Most frequent Events error messages are explained here.
Related topics:





