Event format

Advanced Standard

Preview — Eventarc Advanced

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

Eventarc delivers events, regardless of provider, to the target destination in a CloudEvents (cloudevents.io) format in binary content mode.

CloudEvents is the Cloud Native Computing Foundation's open standard specification for describing event metadata in a common way. Using a standard way to describe event metadata ensures consistency, accessibility, and portability.

A CloudEvent in binary content mode has its context attributes described as HTTP headers. The names of the HTTP headers are the context attribute names prefixed with ce-. The Content-Type header reflects the media type in which the event data is encoded.

Target destinations consume events using an HTTP protocol binding.

For Workflows destinations, the Workflows service converts the event to a JSON object, and passes the event into the workflow execution as a runtime argument.

Define a message binding (Eventarc Advanced)

You can define a message binding and construct a new HTTP request. For more information, see Transform received events.

Format received events (Eventarc Advanced)

You can configure a pipeline to expect event data in a specific format or, before events are delivered to a destination, you can convert event data from one supported format to another. For example, you might need to route events to an endpoint that only accepts Avro or Protobuf data.