Picture this: you have an event that gets fired into the abyss of an event broker in your microservice architecture. The event broker routes the event according to multiple rules, distributes multiple copies to different consumers and persists the event until it’s acknowledged. You might be wondering: how can I observe this event through the organization from event creation to its ultimate destination(s)--including all the opaque hops it took in the event broker?

Event-driven architecture (EDA) is all around us, and we may interact with EDA-based systems daily without even knowing it. It is the architectural backbone of many retail banks, capital markets, e-commerce platforms, and airlines. With hundreds, and even thousands, of applications and microservices connected to an event broker, it can be challenging to retrofit tracing and answer questions like “Where are the events going in the event broker?”, “Are the expected events being published?”, and the infamous “Are consumers throwing away events?”

Attend this talk to learn more about:

- What Event-driven architecture is all about

- Where OpenTelemetry and true end-to-end observability fits in the EDA between applications, APIs and event brokers

- Challenges with current observability implementation in messaging protocols including MQTT, AMQP, Kafka and other industry used event brokers