Eventarc entrega eventos, sin importar el proveedor, al destino objetivo en un formato de CloudEvents (cloudevents.io) en modo de contenido binario.
CloudEvents es la especificación de estándar abierto de la Cloud Native Computing Foundation para describir metadatos de eventos de forma común. Usar una manera estándar para describir los metadatos de eventos garantiza la coherencia, la accesibilidad y la portabilidad.
Un CloudEvent en modo de contenido binario tiene sus atributos de contexto descritos como encabezados HTTP. Los nombres de los encabezados HTTP son los nombres de los atributos de contexto con el prefijo ce-. El encabezado Content-Type refleja el tipo de medio en el que se codifican los datos del evento.
Para los destinos de Workflows, el servicio de Workflows convierte el evento en un objeto JSON y lo pasa a la ejecución del flujo de trabajo como un argumento del entorno de ejecución.
Define una vinculación de mensajes (Eventarc Advanced)
Formatea los eventos recibidos (Eventarc Advanced)
Puedes configurar una canalización para que espere datos de eventos en un formato específico o, antes de que los eventos se entreguen a un destino, puedes convertir los datos de eventos de un formato compatible a otro. Por ejemplo, es posible que debas enrutar eventos a un extremo que solo acepte datos de Avro o Protobuf. Se admiten las siguientes conversiones de formato:
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eEventarc delivers events in CloudEvents format, which is an open standard for describing event metadata, ensuring consistency, accessibility, and portability.\u003c/p\u003e\n"],["\u003cp\u003eEvent data in binary content mode has context attributes described as HTTP headers prefixed with \u003ccode\u003ece-\u003c/code\u003e, and the \u003ccode\u003eContent-Type\u003c/code\u003e header reflects the media type.\u003c/p\u003e\n"],["\u003cp\u003eTarget destinations receive events using an HTTP protocol binding, while Workflows destinations receive a JSON object representation of the event.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Advanced allows users to define a message binding to construct a new HTTP request, enabling transformations of received events.\u003c/p\u003e\n"],["\u003cp\u003eEventarc Advanced supports format conversions between Avro, JSON, and Protobuf, allowing events to be delivered in various formats to meet endpoint requirements.\u003c/p\u003e\n"]]],[],null,["# Event format\n\n[Advanced](/eventarc/advanced/docs/overview) [Standard](/eventarc/standard/docs/overview)\n\nEventarc delivers events, regardless of provider, to the target\ndestination in a CloudEvents ([cloudevents.io](http://cloudevents.io/)) format\nin binary content mode.\n\nCloudEvents is the Cloud Native Computing Foundation's\n[open standard specification](https://github.com/cloudevents/spec) for\ndescribing event metadata in a common way. Using a standard way to describe\nevent metadata ensures consistency, accessibility, and portability.\n\nA CloudEvent in binary content mode has its context attributes described as HTTP\nheaders. The names of the HTTP headers are the context attribute names prefixed\nwith `ce-`. The `Content-Type` header reflects the media type in which the event\ndata is encoded.\n\nTarget destinations consume events using an\n[HTTP protocol binding](/eventarc/docs/cloudevents).\n\nFor Workflows destinations, the Workflows service\nconverts the event to a [JSON object](/eventarc/docs/cloudevents-json), and\npasses the event into the workflow execution as a runtime argument.\n\nDefine a message binding (Eventarc Advanced)\n--------------------------------------------\n\nYou can define a message binding and construct a new HTTP request. For more\ninformation, see\n[Transform received events](/eventarc/advanced/docs/receive-events/transform-events#message-binding).\n\nFormat received events (Eventarc Advanced)\n------------------------------------------\n\nYou can configure a pipeline to expect event data in a specific format or,\nbefore events are delivered to a destination, you can convert event data from\none supported format to another. For example, you might need to route events to\nan endpoint that only accepts Avro or Protobuf data. The following format\nconversions are supported:\n\n- Avro to JSON\n- Avro to Protobuf\n- JSON to Avro\n- JSON to Protobuf\n- Protobuf to Avro\n- Protobuf to JSON\n\nFor more information, see\n[Format received events](/eventarc/advanced/docs/receive-events/configure-format-events)."]]