Outbound Connectors send copies of your telemetry to external systems while Proxus continues to store data internally. Use them to feed data lakes, analytics platforms, or enterprise messaging backbones.
Connector Categories
Pick the connector family that matches your target system:
- Analytics: Splunk, Azure Data Lake
- HTTP API: HTTP API
- Databases: ClickHouse, PostgreSQL, MySQL, SQL Server, Oracle, SQLite, Firebird, DB2, InfluxDB, Redis, TDengine
- Cloud IoT: AWS IoT Core, Azure IoT Hub, Sparkplug B
- Messaging: MQTT, Apache Kafka, RabbitMQ
When to Use Outbound Connectors
- Enterprise analytics: stream telemetry to your data lake or BI stack.
- IT/OT integration: publish data to Kafka or MQTT for downstream services.
- Cloud ingestion: forward device data to managed IoT platforms.
- Rule-driven exports: trigger outbound channels from the Rules Engine when conditions match.
If you are looking for device connectivity (OPC UA, Modbus, Siemens S7, etc.), see Protocols.