Available output connectors

ArcGIS GeoEvent Server can send event data it has received to a variety of destinations. An output connector must recognize the communication channel over which it sends the data and be able to translate event records to an expected format. These tasks are managed by adapters and transports—technical implementations beneath each and every connector.

Learn more about GeoEvent Server adapters and transports

Output connectors

GeoEvent Server output connectors are described below:

Output types	Output connectors
ArcGIS Server	Add a feature Update a feature
Email	Send an email
File	Write to a CSV file Write to a GeoJSON file Write to a JSON file
Instant message	Send an instant message
Kafka	Write GeoJSON to a Kafka topic Write JSON to a Kafka topic Write text to a Kafka topic
Socket	Publish text to a UDP socket Push text to an external TCP socket
Spatiotemporal big data store	Add a feature to a spatiotemporal big data store Update a feature in a spatiotemporal big data store
Stream service	Send features to a stream service
Text message	Send a text message
Web	Push GeoJSON to an external website Push JSON to an external website
WebSocket	Push GeoJSON to an wxternal websocket Push JSON to an external websocket

ArcGIS GeoEvent Server gallery output connectors are described below:

Output types	Output connectors
ActiveMQ	Send text to ActiveMQ
MQTT	Push CSV to an external MQTT message broker Push JSON to an external MQTT message broker Push XML to an external MQTT message broker
RabbitMQ	Send text to RabbitMQ

Other output connectors

If the available connectors do not provide the flexibility you need, you can customize existing connectors or create your own using GeoEvent Manager, or develop your own connectors using the GeoEvent Server Software Development Kit (SDK).

Learn more about customizing and developing your own GeoEvent Server connector

If you have ideas for new output connectors, post them on the ArcGIS GeoEvent Server Ideas page in Esri Community.