Help Center

Events log schema


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, file event.log

Event log is a text file in JSON format and each event is a new line. Default logging level is "Info" (events inform about job being created/deleted, transfer jobs competed, paused/unpaused, agents shut down or starte). This level can be changed in Agent or Job profile and new types of events added or removed from record. Different types of event have common part and event specific part.

Event details of Synchronization, Distribution and Consolidation jobs

COMMON FIELDS

"peer" agent ID, can be found as "AGENT_ID" tag in agent properties
"agent_name" agent where the given event occurred 
"events" the event itself, specific part, its body depends on event type and source, see below.
"id" ordinal event number 
"ts" event timestamp (unixtime)
"t" event type (1=Error, 2=Warning, 3=Info, 4=Trace, 5=File event)
"e" event name
"src" type of the event, see below for details.
"data" id of the event, gets incremented by 1 for a new event from the agent.

Types of events are: Error, Warning, Info, Trace and File event. Sources are: app, job, file activity, other agents and tracker.

Schema: 

 

App

"src": "app"

Error

  • Sync consumes too much memory. It may run slower than usual
  • Bind port <port_number> is busy

Info

  • Startup ("time":"startup time")
  • Shutdown ("uptime":"seconds", "reason":"shutdown_reason", "status":"exit status")
  • Device name changed ("name":"new device name")

Trace

  • Apply policy ("policy_id":"id","success":"boolean","status":"int" -> Mask: FAILED = 0x1, APPLIED = 0x2, NEEDS_NETWORK_RESTART = 0x4,POSTPONED = 0x8)
  • Apply network settings ("interfaces":"list of network interfaces","name":"interface name", "id":"interface id","mac":"device MAC address","type":"wired/wireless", "addrs":"list of addresses")

 

Job

"src":"job_name",
"uid":"HEX transfer id"

Error

<transfer_error_name>

Warning

<transfer_warning_name>

Info

  • Added ("path":"folder_path","access":"RO/RW")
  • Removed
  • Paused ("global:"bool" true if paused through Scheduler)
  • Resumed ("global":"boolean")
  • Completed ("etime":"transfer execution time","err":"transfer error")

Trace

<script events are not for script job!>

  • Start script ("script":"script name")
  • Finish script ("script": "script name, "code: exit code")
  • Start indexing ("initial":"first time indexing or not", "total": current folder state, if initial=false{"files","size"})
  • Finish indexing ("initial":"first time indexing or not", "total": current folder state, if initial=false {"files", "size"})
  • Start data transfer ("total":{"files", "size"}, "local:{"files","size"}, "queue":(if not empty):{"files","size"})
  • Finish data transfer ("total":{"files", "size"}, "local:{"files", "size"}, "queue":(if not empty):{"files", "size"})
  • Got N peers ("tracker IP:Port", "transport":"protocol")

File

"src":"job_name",
"uid":"HEX transfer id"

Warning

  • Conflict file created for "<file_name>" ("<new_local_path>")
  • File "<local_path>" is modified
  • File "<local_path>" is too large (to be written to file system)
  • File "<local_path>" is locked
  • No access to file "<local_path>"


Trace

  • File "<local_path>" is unlocked
  • Got access to file "<local_path>"

File event

  • Added file "<file_name>" ("by_peer":"PeerId string" if by remote peer, "path", "size")
  • Deleted file "<file_name>" ("by_peer":"PeerId string" if by remote peer, "hash" if it's local file, "path", "size")
  • Updated file "<file_name>" ("by_peer":"PeerId string" if by remote peer, "hash" if it's local file, "path", "size")
  • Downloaded file "<file_name>"
  • File {file_name} was changed on Read-Only agent, it won't be synced 
  • ("hash", "path", "size")

 

Peer

"src":"job_name",
"uid":"HEX transfer id",
"data":for trace{"addr":"peer ip address","v":"peer version","transport":"connection transport" (RELAY, TUNNEL, TCP, uTP, uTP2, UNKNOWN), "priority":"connection priority"}

Error

  • Time difference exceeded. Cannot sync with <peer_name>(error:"error code")
  • Error while syncing with peer <peer_name> (code:<error_code>)(error:"error code")
  • <error_message>. Cannot sync with <peer_name>.(error:"error code")

Warning

  • Time difference exceeded. Cannot sync with <peer_name>(error:"error code")

Trace

  • Connected to peer <peer_name> ("ip", "protocol," "v")
  • Disconnected from peer <peer_name>("ip", "protocol," "v")

 

Tracker

"src":"job_name",
"uid":"HEX transfer id",
"addr":"peer ip address",
"transport":"UTP/TCP"

Error

  • Failed connect to tracker (if LB mode)(trackers:{"addr":"tracker ip address","protocol":"tracker protocol","code":"error code","str":"error message")

Warning

  • No peers found("addr":"peer ip address","transport":"UTP/TCP")
  • Failed connect to tracker (if HA mode has working tracker)(trackers:{"addr":"tracker ip address","protocol":"tracker protocol","code":"error code","str":"error message")

Trace

  • Got peers ("addr":"peer ip address","transport":"UTP/TCP")

 

Event details of Script jobs

"src":"job_name",
"uid":"HEX transfer id

Error

  • <std_err>: (Linux & Mac)

Trace

  • <std_out>
  • <std_err> : (WIN only)

 

 

 

 

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.