Help Center

Understanding events log on Management Console


Events log keeps records of events related to each job. 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 of Synchronization, Distribution and Consolidation jobs

Events marked with an asterisk (*) are available only for a Synchronization job.

PER SHARE EVENTS

"peer" agent ID, can be found as "AGENT_ID" tag in agent properties
"agent_name" agent where the given event occurred 
"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, see below for details.
"id" id of the event, gets incremented by 1 for a new event from the agent.
"ts" timestamp of the event in UNXTIME format 
"script" type of the post command in Distribution or Consolidation job. Can be:
pre-indexing (command will be executed before transfer):
complete (command will be executed after an agent finishes transfer)
post-downloading (command will be executed after all agents finish transfer)

 

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 where the given event occurred 
"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, see below for details.
"id" id of the event, gets incremented by 1 for a new event from the agent.
"ts" timestamp of the event in UNXTIME format

 

 

event_type Meaning Job where it's reported
 folder_added  the share was created on the agent  Sync
 transfer_added  transfer folder was created  Distribution, Consolidation
 transfer completed  transfer is complete  Distribution, Consolidation
 folder_receive_start  files in the share started downloading  Sync
 folder_receive_finish  all currently available files are downloaded  Sync
     
file_added a new file was found, will be added to database as new entry  Sync, Distribution,  Consolidation
file_modified changes in file's size or timestamp was detected, file will be rechecked  Sync
file_received finished downloading all pieces of the file from other agents  Sync,  Distribution, Consolidation
file_deleted file was removed from either local or remote agent  Sync
file_deletion_received  agent received notification that a remote agent deleted a file. This agent will now remove its local copy  Sync
     
script_started agent started executing script  Script, Distribution, Consolidation
script_finished agent finished executing script  Script, Distribution, Consolidation

 

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.