Eventarc allows events to be asynchronously delivered from third-party providers to interested subscribers. For details, see Third-party events in Eventarc.
The following information is required when you register as an event provider using this form.
Ensure that all the details you provide are accurate and complete. If you have any questions or for more information, contact firstname.lastname@example.org.
|Provider display name||
The event provider name. This name will be visible to event subscribers through the Eventarc interface.
For example: "Company Name"
An identifier that subscribers will use when subscribing to events from the event provider.
The name should consist of lowercase alphanumeric characters.
A list of regions supported by the event provider. Subscribers will only be able to subscribe to events (that is, create channels and triggers) for this event provider in these regions.
This list must be a subset of the regions supported by Eventarc. It is expected that all Eventarc regions will be supported in due course; until then, you can ask for the addition of new regions through the registration form.
Note that dual and multi-regions are currently not supported for third-party events.
|Publisher project||The Google Cloud project ID that the event provider will use to publish events. You can find your project ID on the Dashboard page of the Google Cloud console.|
The list of event types published by the event provider. A subscriber's trigger can route exactly one event type from one event provider.
Event types must follow the format:
If you do not supply any event types, the default event type of
|Event type description(for each event type)||A user-visible description of each event type.|
|Event attributes(for each event type)||
This is the list of attributes available to filter events of each event type. Each attribute can be included (with any value) as an extension context attribute in any published event.
Each subscriber's trigger can filter on these attributes to limit the events matched and delivered to the trigger destination.
|Development and test information||Description|
|Test subscriber projects||A list of Google Cloud project IDs authorized to subscribe to events for testing or during any alpha period. You can find project IDs on the Dashboard page of the console.|
|Contact email||The email address to which information should be sent.|
|Customer issues||For any customer problems related to your events, how you would like Eventarc to convey these issues to you.|