Before going to more depths, let's see what an "event" is. Event is a text message in a format loosely based on those of famous Internet protocols such as SIP, SMTP, and HTTP: many "headers" (key/value pairs) and possibly one "body" (free form payload):
Event-Name: RE_SCHEDULE Core-UUID: 6ddf010e-bc0b-4366-8413-6becd7f77076 FreeSWITCH-Hostname: lxc111 FreeSWITCH-Switchname: lxc111 FreeSWITCH-IPv4: 192.168.1.111 FreeSWITCH-IPv6: 2001%3Ab07%3A5d32%3A860b%3Aa067%3A61ff%3Afe4f%3A2119 Event-Date-Local: 2017-06-26%2018%3A39%3A51 Event-Date-GMT: Mon,%2026%20Jun%202017%2018%3A39%3A51%20GMT Event-Date-Timestamp: 1498502391402930 Event-Calling-File: switch_scheduler.c Event-Calling-Function: switch_scheduler_execute Event-Calling-Line-Number: 71 Event-Sequence: 22105 Task-ID: 1 Task-Desc: heartbeat Task-Group: core Task-Runtime: 1498502411
This is the dump of one of the easiest events to spot, the rescheduling of the heartbeat (an internal FreeSWITCH...