Event-based introspection protocol for landscape and event exchange monitoring

A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform one or more operations for event-based introspection protocol for landscape and event exchange monitoring, comprising:

• subscribing, by an event client and with a messaging infrastructure, as an event client;
• publishing, by the event client and to the messaging infrastructure, a client connected message;
• publishing, by the event client, and to the messaging infrastructure, a client alive ping message;
• consuming, by the event client and from the messaging infrastructure, event data from one or more other event clients subscribed to the messaging infrastructure;
• processing, by the event client and based on the consumed event data from one or more other event clients, status information;
• adding, by the event client and to a status table, the processed status information;
• and
• sending, by the event client and to the messaging infrastructure, a client disconnected message to disconnect from the messaging infrastructure.

A computer-implemented system for event-based introspection protocol for landscape and event exchange monitoring, comprising:

• one or more computers;
• and
• one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations, comprising:
• subscribing, by an event client and with a messaging infrastructure, as an event client;
• publishing, by the event client and to the messaging infrastructure, a client connected message;
• publishing, by the event client, and to the messaging infrastructure, a client alive ping message;
• consuming, by the event client and from the messaging infrastructure, event data from one or more other event clients subscribed to the messaging infrastructure;
• processing, by the event client and based on the consumed event data from one or more other event clients, status information;
• adding, by the event client and to a status table, the processed status information;
• and
• sending, by the event client and to the messaging infrastructure, a client disconnected message to disconnect from the messaging infrastructure.