Skip to content

Data Flow Engine - Sinks


When the EventSink receives a message, it creates an event based on the configured parameters and forwards it to the Event Management Service.

Field Mapping

The EventSink supports field mapping: It maps attributes from the incoming message to fields of the event it creates. The mapping is defined by a JSON string, which is provided in the field-mapping-json property of the EventSink. This also allows mapping static values to event parameters. The following event parameters can be defined using field mapping:

  • description
  • source
  • code
  • severity
  • acknowledged
  • custom fields

For details, refer to the field-mapping-json property in the EventSink Specification.

Custom Event Type

The EventSink can be used with pre-made custom event types. The following picture shows how the app searches for an event type, which has been set in stream definition: Searching process for event types


Custom event types must be created before stream deployment using the Event Management Service, refer to the samples.


The EmailSink sends an e-mail when it receives a message from the stream. It uses the Notification Service for sending the e-mail and requires that a categoryID has already been created. Instructions for creating a categoryID are available in the Notification Service documentation. When time series data arrives at the EmailSink, the application creates the e-mail payload and posts a request to the Notification Service to send the e-mail. The EmailSink sends the same message every time it is triggered by the stream.

Any questions left?

Ask the community

Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.