Help Center

Understanding events log on Management Console


Events log keeps records of events related to Synchronization jobs. Management Console receives these events from agents. It's located in Console's storage folder, "data" subfolder.

 

Event log is a text file in JSON format. Each line is a separate event, per share or per file. 

Event details 

Per share events: 

"peer" agent ID, can be found as "AGENT_ID" tag in agent properties
"agent_name" agent name as it is displayed in "Agents" tab of MC
"job_name" the name of the job where event belongs to
"share" unique shareID, as it is referred in debug logs
"event_type" type of the event: 
 - folder_added (the share was created on the agent), 
 - folder_receive_start (files in the share started downloading)
 - folder_receive_finish (all currently available files are downloaded)
"id" id of the event, gets incremented by 1 for a new event from the agent.
"ts" timestamp of the event in UNXTIME format 

 

Per file events:

"peer" agent ID, can be found as "AGENT_ID" tag in agent properties
"error" error code of the operation attempted 
"job_name" the name of the job where event belongs to
"agent_name" agent name as it is displayed in "Agents" tab of MC 
"hash" internal format hash of the file
"path" path to the file, relatively the share 
"share" unique shareID, as it is referred in debug logs
"size" new size of the file, actual for the moment of capturing event
"event_type" type of the event:
 - file_added (a new file was found, will be added to database as new entry)
 - file_modified (changes in file's size or timestamp was detected, file will be rechecked)
 - file_received (finished downloading all pieces of the file from other agents)
 - file_deleted (file was removed from either local or remote agent) 
"id" id of the event, gets incremented by 1 for a new event from the agent.
"ts" timestamp of the event in UNXTIME format

Events timing

All events arrive with the granularity of timestamp of 1 second. It is advised to sort the events according to "ts" field as they may arrive out of order.

Events redundancy 

The events "file_added" may be complemented with "file_modified" event as it is notified by OS itself. Every file modification spotted by OS will also spawn a new "file_modified" event.

 

 

 

Was the article helpful? Yes / No, send feedback on article Thanks!


Please note that we won't mail you back. This is just purely feedback on the article above. If you need help from our Support Team, please use the "Contact Support" link at the top of the page.