Skip to content

Commit c0c7252

Browse files
committed
Fixed issues
1 parent 08d9056 commit c0c7252

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

articles/event-grid/.openpublishing.redirection.event-grid.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"redirections": [
33

44
{
5-
"source_path": "event-hubs-integration.md",
5+
"source_path": "event-grid-event-hubs-integration.md",
66
"redirect_url": "/azure/event-grid/event-hubs-integration",
77
"redirect_document_id": false
88
},

articles/event-grid/event-schema-resource-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Azure subscriptions and resource groups emit the same event types. The event typ
1313

1414
Resource events are created for PUT, PATCH, POST, and DELETE operations that are sent to `management.azure.com`. GET operations don't create events. Operations sent to the data plane (like `myaccount.blob.core.windows.net`) don't create events. The action events provide event data for operations like listing the keys for a resource.
1515

16-
When you subscribe to events for a resource group, your endpoint receives all events for that resource group. The events can include event you want to see, such as updating a virtual machine, but also events that maybe aren't important to you, such as writing a new entry in the deployment history. You can receive all events at your endpoint and write code that processes the events you want to handle. Or, you can set a filter when creating the event subscription.
16+
When you subscribe to events for a resource group, your endpoint receives all events for that resource group. The events can include event you want to see, such as updating a virtual machine, but also events that aren't important to you, such as writing a new entry in the deployment history. You can receive all events at your endpoint and write code that processes the events you want to handle. Or, you can set a filter when creating the event subscription.
1717

1818
To programmatically handle events, you can sort events by looking at the `operationName` value. For example, your event endpoint might only process events for operations that are equal to `Microsoft.Compute/virtualMachines/write` or `Microsoft.Storage/storageAccounts/write`.
1919

articles/event-hubs/azure-event-hubs-kafka-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ The most common reason Azure Event Hubs customers ask for Kafka Streams support
130130
Standalone and without ksqlDB, Kafka Streams has fewer capabilities than many alternative frameworks and services, most of which have built-in streaming SQL interfaces, and all of which integrate with Azure Event Hubs today:
131131

132132
- [Azure Stream Analytics](../stream-analytics/stream-analytics-introduction.md)
133-
- [Azure Synapse Analytics (via Event Hubs Capture)](../event-grid/event-grid-event-hubs-integration.md)
133+
- [Azure Synapse Analytics (via Event Hubs Capture)](../event-grid/event-hubs-integration.md)
134134
- [Azure Databricks](/azure/databricks/scenarios/databricks-stream-from-eventhubs)
135135
- [Apache Samza](https://samza.apache.org/learn/documentation/latest/connectors/eventhubs)
136136
- [Apache Storm](event-hubs-storm-getstarted-receive.md)

0 commit comments

Comments
 (0)