Skip to main content

General

Outbound Connectors Overview

Export telemetry to databases, messaging systems, cloud platforms, and HTTP endpoints.

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.

Outbound Connector Architecture
developer_board

Edge Gateway

Data Source

call_split

Outbound Router

Parallel Dispatch

storage

Databases

ClickHouse / Postgres

message

Messaging

Kafka / MQTT

cloud

Cloud IoT

AWS / Azure

Connector Categories

Databases

ConnectorPageDescription
ClickHouseGuideHigh-performance columnar OLAP with Async Inserts and LZ4
PostgreSQLGuideRelational database with auto table creation
MySQLGuideRelational database with batch inserts
SQL ServerGuideMicrosoft SQL Server with bulk copy
OracleGuideEnterprise database with batch operations
InfluxDBGuideTime-series database with line protocol
RedisGuideIn-memory key-value store with pub/sub
TDengineGuideTime-series database with WebSocket and Super Tables
SQLiteGuideLightweight local database
FirebirdGuideEmbedded/server relational database
IBM DB2GuideEnterprise mainframe database

Messaging

ConnectorPageDescription
MQTTGuideQoS support, TLS, in-memory reactive buffering
Apache KafkaGuideHigh-throughput with partitioning and replication
RabbitMQGuideAMQP protocol with exchanges and routing keys

Cloud IoT

ConnectorPageDescription
AWS IoT CoreGuideX.509 certificate auth over MQTT
Azure IoT HubGuideDevice telemetry via MQTT over TLS
Sparkplug BGuideEclipse Sparkplug B with device lifecycle

Analytics & API

ConnectorPageDescription
SplunkGuideHEC forwarding with SSL and acknowledgment
Azure Data LakeGuideGen2 export with Parquet, JSON, and CSV
HTTP APIGuideFlexible HTTP export with authentication

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.