Event streams: questions about topics, throughput and consumer lag
Event streams carry orders, clicks, payments and telemetry as they happen. The questions people ask of them are usually operational: is a consumer falling behind, did volume drop, which producers changed their schema.
These connectors will read stream metadata and the events a person is allowed to see, under the platform's own access controls.
Events & streaming connectors
Amazon Kinesis analytics: ask about stream throughput, shard counts, iterator age, throttled writes and Firehose delivery failures in plain language.
Status: AvailableAzure Event Hubs integration for questions on incoming and outgoing messages, throttled requests, consumer group checkpoints and Capture output.
Status: AvailableGoogle Pub/Sub integration for questions about topics, subscriptions, unacked backlog, oldest message age and dead-letter traffic across projects.
Status: AvailableKafka MCP questions over Apache Kafka and Confluent: topic throughput, partition skew, consumer group lag, connector failures and Schema Registry subjects.
Status: Available
Questions that cross these systems
- Which consumer groups are more than ten minutes behind on the orders topic?
- How did event volume per hour change after yesterday's release?
- Which topics had schema changes registered this week?
Questions and answers
- Will Nexatron store my event stream?
- No. The connectors will read stream metadata and sample or aggregate events on request. Long-term analysis belongs in the warehouse the stream already lands in, which Nexatron can answer today.
Need a system from this list?
Tell us which system and which questions, and we will scope a pilot on your own data.