Starting with Resilio Connect v 2.4.0, each agent records ongoing events and can show them in Management Console UI. Basically, these are text files that are locally stored in agents’ storage folder in “events” subdirectory and rotate - when log file reaches 100MB, it’s zipped up and kept for as many days as Event logs max age (days) in Agent profile says, default is 30 days. Events older than that cannot be viewed in UI. Management Console will retrieve only those event types that are masked in Agent or Job profiles, parameter "Console's events detalization".
Important NoteAgents older than v.2.4.0 won’t be able to show their events.
Download the log file locally
To view the events double-click on a job and click on “Show” button in the column. Events will be fetched from agent’s log files to Management Console via HTTPS POST request. They’ll be stored in MC’s storage folder, “clients-logs/scripts” subdirectory and appear in UI. By default events cover 1 hour and this time period is configurable. Events do not refresh in real-time, use “Refresh” button to see latest events. Admin can download the log file locally so as to examine it with a third-party tool, for example, Splunk.
If agent is offline
If an agent is offline and/or not connected to MC, it’ll be able to show only those events it fetched before, if any. Attempt to fetch fresh events will result in “Waiting….” status.
If MC can't find the log file
If the events log files are physically missing from agent’s or Console’s storage folder (see above), error “File not found” will be seen. Events can be filtered in real time by two parameters - type and source. Additionally, filtered and non-filtered events can be searched for a pattern.
View event logs directly in MC (from v.2.5 and up)
Starting with Resilio Connect v.2.5.0, agent event logs can be viewed in agent details.
These are locally stored both in the Agent's and Console's storage folder as a database file
Event types are:
Error shows errors that agent encounters. Errors prevent agents from synchronizing files and completing the job, and these might be signaling about failed connection to tracker, time difference between agents, lack of permissions to access files, running out of storage space, failed script etc.
Warning, as opposed to errors do not stop syncing, but are just informing about some minor
Info events inform about job being created/deleted, transfer jobs competed, paused/unpaused, agents shut down or started.
Trace events are most substantive. They show step-by-step job execution - deploying job policy, applying new settings, starting and finishing scripts, discovering other agents, indexing and transferring files, closing connections upon completing the job.
File events are those related to files themselves, like new file added, deleted or updated by the agent.
Sources of events are App (the agent process itself) and Transfer (job). App source informs about applying profile settings. Transfer events are all types of events referring to job and file transfer.
Full events log schema is available here.