Cortex in depth
The Cortex chapter shows the canvas where you see devices, groups, and data destinations. This chapter goes deeper: what you can actually configure on an endpoint, what destination types exist, and how you monitor a route and keep it error-free.
Groups and routing
A Group combines several devices so you can forward them together to one or more destinations, instead of wiring up every device individually. You create one on the canvas via Create Group.
Destination types for endpoints
When creating an endpoint, you choose one of the following types:
- Webhook — an HTTP call to a URL you specify.
- MQTT Forward — delivery to your own MQTT broker.
- AMQP — delivery to your own AMQP broker.
- REST Pull API — the platform makes the data available so your system actively fetches it, instead of it being delivered.
- Pallax Analytics — forwarding into this platform's own Analytics chapters (see Dashboards).
- Custom Endpoint — your own protocol and your own payload format, when none of the preceding types fit.
- OPC UA Endpoint — delivery to your own OPC UA server.
More destination types (Pulsar, Kinesis, Pub/Sub, Event Hub) are already marked "Soon" in the interface, but aren't available yet.
For each route you also set the Data Format: decoded values only (see Decoder), raw data only, or both together.