This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can trysigning in orchanging directories.
Access to this page requires authorization. You can trychanging directories.
This article builds on theWhat is Azure Event Grid? article to provide essential information before you start using Event Grid’s pull and push delivery over HTTP. It covers fundamental concepts, resource models, and message delivery modes supported. At the end of this document, you find useful links to articles that guide you on how to use Event Grid and to articles that offer in-depth conceptual information.
Important
This document helps you get started with Event Grid capabilities that use the HTTP protocol. This article is suitable for users who need to integrate applications on the cloud. If you require to communicate IoT device data, seeOverview of the MQTT Support in Azure Event Grid.
Event Grid conforms to CNCF’s open standardCloudEvents 1.0 specification using theHTTP protocol binding withJSON format. It means that your solutions publish and consume event messages using a format like the following example:
{ "specversion" : "1.0", "type" : "com.yourcompany.order.created", "source" : "https://yourcompany.com/orders/", "subject" : "O-28964", "id" : "A234-1234-1234", "time" : "2018-04-05T17:31:00Z", "comexampleextension1" : "value", "comexampleothervalue" : 5, "datacontenttype" : "application/json", "data" : { "orderId" : "O-28964", "URL" : "https://com.yourcompany/orders/O-28964" }}Anevent is the smallest amount of information that fully describes something that happened in a system. We often refer to an event as shown above as a discrete event because it represents a distinct, self-standing fact about a system that provides an insight that can be actionable. Examples include:com.yourcompany.Orders.OrderCreated,org.yourorg.GeneralLedger.AccountChanged,io.solutionname.Auth.MaximumNumberOfUserLoginAttemptsReached.
Note
We interchangeably use the termsdiscrete events,cloudevents, or justevents to refer to those messages that inform about a change of a system state.
For more information on events, see the Event GridTerminology.
The user community also refers to events to those type of messages that carry a data point, such as a single reading from a device or a single click on a web application page. That kind of event is usually analyzed over a time window or event stream size to derive insights and take an action. In Event Grid’s documentation, we refer to that kind of event asdata point,streaming data, ortelemetry. They're a kind of data that Event Grid’s MQTT support and Azure Event Hubs usually handle.
Events published to Event Grid land on atopic, which is a resource that logically contains all events. Anevent subscription is a configuration resource associated with a single topic. Among other things, you use an event subscription to set event selection criteria to define the event collection available to a subscriber out of the total set of events present in a topic.
Push delivery is supported for the following resources. Click on the links to learn more about each of them.
Configure an event subscription on a system, custom, or partner topic to specify a filtering criteria for events and to set a destination to one of the supportedevent handlers.
The following diagram illustrates the resources that support push delivery with some of the supported event handlers.
Note
If you are interested to know more about push delivery on Event Grid namespaces, see [namespace-push-delivery-overview.md].
The following articles provide you with information on how to use Event Grid or provide you with additional information on concepts.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?
Was this page helpful?
Want to try using Ask Learn to clarify or guide you through this topic?