Publish DeviceChain rule actions to Apache Kafka
A DeviceChain rule can do more than raise an alarm. Its publish action sends a message you shape with CEL to a connector, and one of the connector types is Apache Kafka. A separate outbound-connectors service delivers it, so a slow or failing broker affects only connector delivery, never detection.
A connector is a versioned resource
A connector is a tenant-scoped resource with the same lifecycle as a device profile or a dashboard: you edit a draft, publish an immutable version, and roll back if a change misbehaves. It holds the type, the destination configuration (broker addresses and topic for Kafka) and an optional credential referenced by handle. The credential is written to the secret store and never returned in cleartext.
The Kafka connector supports TLS and the SASL mechanisms PLAIN, SCRAM-SHA-256 and SCRAM-SHA-512. You configure and credential a connector once and reuse it across as many rules as you like, and the credential never appears in a rule.
How delivery works
When a publish action fires, the detection engine hands a dispatch request, with an idempotency key derived from the firing, to the outbound-connectors service over the internal message bus, and goes back to detecting. The request is durable and delivery is at-least-once, so a consumer should tolerate a repeat. An action over a tenant's budget is recorded and not retried. Payloads are shaped only with CEL, so what a rule can send is bounded and reviewable.
Where it may send
Every connection is checked at the moment it is made, against the address the destination actually resolved to. Loopback, private, carrier-grade NAT, link-local and cloud-metadata addresses are refused by default, and for Kafka every broker the cluster advertises in its metadata is checked as well, not only the addresses you configured. An operator can permit specific private addresses, which is how an in-cluster broker or Amazon MSK is reached.
Outbound actions are also governed per tenant, with a platform default ceiling that is never unlimited.
What it does not do.
- The Kafka connector is one-way: it publishes, and it does not consume.
- The outbound-connectors service ships in the full deployment profile, not in default, so an instance has to be brought up on the full profile to run it.
- The supported connector types today are MQTT, Kafka, Amazon SNS and Amazon SQS, plus the httpCall webhook action.