Skip to main content

Event Grid Adapter

ConnXio (CX) lets customers provide messages to the CX pipeline by leveraging Azure Event Grid. This page details how to configure Event Grid in CX but does not describe how to set up or configure Event Grid itself, please refer to the Microsoft documentation for more information about Event Grid.

Limitations​

At this point in time we only support the Blob Storage for Event Grid. Adding new options is possible, please contact us if you need other options.

There are very few limitations on Azure Event Grid communication. Since Event Grid functions as a event emitter towards the CX Api the only limitations are on bandwidth and traffic. The CX Api scales with traffic and is thoroughly monitored and should handle a lot of traffic, if you have peak loads of thousands of messages per second we do recommend looking at queue options instead to mitigate risk.

Configuring Event Grid message intake​

To configure CX to start processing your event grid events select the Event Grid option in "Inbound Connection" shape:

img

A new window pops up. Add data as seen below:

img

  • Connection String Security Configuration: Reference to the Security Configuration that contains the connection string to the Storage Account that holds the data represented by the message sent to the API from Event Grid.
  • Event Grid Blob Container Name List: A comma separated list over possible containers referenced in the EventGrid message.

Configuring Event Grid endpoints in Azure needs picture of correlationid​

Please refer to the Swagger documentation for what parameters are accepted for the CX EventGrid endpoint. As with other Api endpoints (as described on the Api page only CorrelationId is required for new integrations.

Event grid uses simple authentication patterns and does, at the point of writing, not support OAuth 2.0. Since this is the case we accept OCP token verification through APIM. Supply this by configuring the APIM uri https://cmh-messagehub-apim-prod.azure-api.net with query parameters in your Event Grid configuration in Azure like so:

https://cmh-messagehub-apim-prod.azure-api.net/api/eventgrid?subscription-key=xxxx-xxxx-xxx-xxxx-xxxx&ConfigCorrelationId=xxxx-xxxx-xxx-xxxx

Where subscription-key refers to your authentication key supplied by your ConnXio representative, and ConfigCorrelationId refers to the Id of the integration in the portal.

Retry​

Retry on Event Grid is handled by the Event Grid itself. Please refer to the Microsoft Documentation.