Cloud-native event buses
Route computed Genesys KPI events into serverless and cloud-native consumers — Azure Functions, Logic Apps, AWS Lambda, Step Functions — without maintaining always-on polling services.
Discrete events, not just streams
When a KPI crosses a threshold or a state changes, a discrete event can trigger serverless automation directly. Many Azure estates use both: Event Hubs for the continuous stream and Event Grid for actionable, fan-out events.
Targets in this category
4 targets · 0 implemented / proven
Azure Event Grid
Trigger Functions, Logic Apps and custom webhooks.
AWS EventBridge
Lambda and Step Functions routing.
Google Eventarc
Cloud Run and Workflows triggers.
Azure Event Hubs
High-throughput streaming companion.
Why it matters
Actionable KPI events
CloudEvents-compatible payloads carry the reactive processing KPI envelope to whatever serverless consumer needs to act.
From SLA breach to serverless action
The publisher emits discrete events to an Event Grid topic; a Function, Logic App or downstream SaaS reacts immediately — no polling service to keep alive. Pair with Event Hubs when you also need the continuous analytics stream.
- CloudEvents-compatible JSON with the KPI envelope
- Fan-out to multiple serverless subscribers
- Event Grid for actions, Event Hubs for streams
Choosing
Event Grid vs Event Hubs
Two jobs: discrete actions and continuous streams.
| Event Grid | Event Hubs | |
|---|---|---|
| Model | Discrete events, fan-out | High-throughput streaming |
| Volume | KPI threshold / state change | Continuous metric stream |
| Genesys fit | Alert on SLA breach | Real-time analytics mesh |
Same engine, same guarantees
Every target inherits the platform
Whichever destination you pick, it runs on the same Reactive Engine — with consistent semantics, client-owned Azure, enterprise security and a delivery lifecycle that fits your estate.
One KPI definition
Every target in this category consumes the same computed metrics — service level is service level, everywhere.
Client-owned Azure
Ingest, reactive processing and storage run inside your subscription. Connectors are the only thing that reaches outward.
Platform-package model
Each target ships as a Global.Platform.* package on the shared core — adding one is a connector, not a rewrite.
Built for your SDLC
Provisioned as code, shipped through your pipelines, secured in Key Vault — like any other service you run.
Map your destinations to the right connectors
Book a connector assessment and we'll match your KPI families to the targets in this category — on your own Azure tenant.
Streamvane by Tessovia · Azure · AWS · GCP · Your data, your keys