Determining an event history for an event processed by a plurality of communicating servers via a central event data log

A computer-implemented method to determine status information for events processed by multiple processors, comprising:

• receiving, by a computing device and from a first processor in response to processing an event by the first processor, first data associated with the event, the first data comprising a first correlation identifier associated with the event and the first processor;
• storing, by the computing device, the first data associated with the event as a first entry in a central data log of a tracing repository;
• receiving, by the computing device and from a second processor, in response to processing the event by the second processor at a first time after processing the event by the first processor, second data associated with the event, the second data comprising a second correlation identifier associated with the event and the second processor and further comprising at least one primary data element in common with the first data;
• storing, by the computing device, the second data associated with the event as a second entry in the central data log of the tracing repository, the stored second data being associated with the stored first data based on the at least one primary data element of the second data in common with the first data;
• receiving, by the computing device, a query;
• generating, by the computing device based on the query, an event status comprising the first entry and the second entry from the central data log;
• and
• outputting, by the computing device, the generated event status.

A computer program product, comprising:

• a non-transitory computer-readable medium having computer-readable program instructions embodied thereon that when executed by a computer cause the computer to determine status information for events processed by multiple processors, the computer readable instructions comprising:
• computer-readable program instructions to receive from a first processor in response to processing an event by the first processor, first data associated with the event, the first data comprising a first correlation identifier associated with the event and the first processor;
• computer-readable program instructions to store the first data associated with the event as a first entry in a central data log of a tracing repository;
• computer-readable program instructions to receive, from a second processor, in response to processing the event by the second processor at a first time after processing the event by the first processor, second data associated with the event, the second data comprising a second correlation identifier associated with the event and the second processor and further comprising at least one primary data element in common with the first data;
• computer-readable program instructions to store the second data associated with the event as a second entry in the central data log of the tracing repository, the stored second data being associated with the stored first data based on the at least one primary data element of the second data in common with the first data;
• computer-readable program instructions to receive a query;
• computer-readable program instructions to generate, based on the query, an event status comprising the first entry and the second entry from the central data log;
• and
• computer-readable program instructions to output the generated event status.

A system to secure a wireless mesh network of beacon devices, comprising, comprising:

• a storage device;
• and
• a processor communicatively coupled to the storage device, wherein the processor executes application code instructions that are stored in the storage device to cause the system to:
• receive, from a first processor in response to processing an event by the first processor, first data associated with the event, the first data comprising a first correlation identifier associated with the event and the first processor;
• store the first data associated with the event as a first entry in a central data log of a tracing repository;
• receive, from a second processor, in response to processing the event by the second processor at a first time after processing the event by the first processor, second data associated with the event, the second data comprising a second correlation identifier associated with the event and the second processor and further comprising at least one primary data element in common with the first data;
• store the second data associated with the event as a second entry in the central data log of the tracing repository, the stored second data being associated with the stored first data based on the at least one primary data element of the second data in common with the first data;
• receive a query;
• generate, based on the query, an event status comprising the first entry and the second entry from the central data log;
• and
• output the generated event status.