Egress Alarms and Conditions

Events are sent to CONNECT data services, Edge Data Store or PI Web API as strings - one string per event.

To create a stream, you can configure the streamID parameter in Data selection or set a default StreamId pattern using the defaultEventStreamIdPattern parameter in Data source. The adapter maintains a read only collection of created types for re-use.

EventStringDelimiter

Event fields from the incoming event notification are extracted and concatenated into a string with a delimiter as specified by the EventStringDelimiter parameter (default pipe ‘|’) in the Configure client settings. These fields correlate to the EventProperties parameter specified during subscription in Data selection.

IncludeEventPropertyName

When specified as true in Client settings, the event details are egressed as Name-Value pairs separated by a colon (:).

Note: When configuring two or more data selection items with different source filters for the same event type, there is a chance that data can be overwritten. While specifying the streamId, if the parameter is set to null or a default stream id pattern is retained, it is possible you could overwrite the data to the same streamId for events generated from different sources (denoted by source name filter).

PI Data Archive and PI Web API egress have string value character limits. PI Data Archive has a limit for String data of up to 972 characters if annotated, 976 otherwise. If the adapter with PI Web API as OMF Egress Data endpoint has an egress string of length greater than 972 characters, PI Web API trims the string to 972 characters and adds [TRUNCATED] to the end of the trimmed value, stores that trimmed value, and returns a 409 (Conflict) error.