You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/howto-develop-event-listener.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,8 +69,8 @@ Find your Azure Web PubSub service from **Azure portal**. Navigate to **Identity
69
69
1. Open this [Event Hubs Consumer Client](https://awpseventlistenerdemo.blob.core.windows.net/eventhub-consumer/index.html) web app, input the Event Hubs connection string to connect to an event hub as a consumer. If you get the Event Hubs connection string from an Event Hubs namespace resource instead of an event hub instance, then you need to specify the event hub name. This event hub consumer client is connected with the mode that only reads new events; the events published before aren't seen here. You can change the consumer client connection mode to read all the available events in the production environment.
70
70
71
71
1. Use this [WebSocket Client](https://awpseventlistenerdemo.blob.core.windows.net/webpubsub-client/websocket-client.html) web app to generate client events. If you've configured to send system event `connected` to that event hub, you should be able to see a printed `connected` event in the Event Hubs consumer client after connecting to Web PubSub service successfully. You can also generate a user event with the app.
72
-
:::image type="content" source="media/howto-develop-event-listener/eventhub-consumer-connected-event.png" alt-text="Screenshot of a printed connected event in the Event Hubs consumer client app":::
73
-
:::image type="content" source="media/howto-develop-event-listener/web-pubsub-client-specify-event-name.png" alt-text="The area of the WebSocket client app to generate a user event":::
72
+
:::image type="content" source="media/howto-develop-event-listener/eventhub-consumer-connected-event.png" alt-text="Screenshot of a printed connected event in the Event Hubs consumer client app.":::
73
+
:::image type="content" source="media/howto-develop-event-listener/web-pubsub-client-specify-event-name.png" alt-text="Screenshot showing the area of the WebSocket client app to generate a user event.":::
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/howto-monitor-azure-policy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ When a resource is non-compliant, there are many possible reasons. To determine
48
48
1. Select **Compliance**.
49
49
1. Use the filters to display by **Scope**, **Type** or **Compliance state**. Use search list by name or
50
50
ID.
51
-
[](./media/howto-monitor-azure-policy/azure-policy-compliance.png#lightbox)
51
+
[](./media/howto-monitor-azure-policy/azure-policy-compliance.png#lightbox)
52
52
1. Select a policy to review aggregate compliance details and events.
53
53
1. Select a specific Web PubSub for resource compliance.
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/howto-troubleshoot-resource-logs.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ Currently Azure Web PubSub supports integration with [Azure Storage](../azure-mo
82
82
83
83
1. Go to Azure portal.
84
84
1. On **Diagnostic settings** page of your Azure Web PubSub service instance, select **+ Add diagnostic setting**.
85
-
:::image type="content" source="./media/howto-troubleshoot-diagnostic-logs/diagnostic-settings-list.png" alt-text="Screenshot of viewing diagnostic settings and create a new one":::
85
+
:::image type="content" source="./media/howto-troubleshoot-diagnostic-logs/diagnostic-settings-list.png" alt-text="Screenshot of viewing diagnostic settings and create a new one.":::
86
86
1. In **Diagnostic setting name**, input the setting name.
87
87
1. In **Category details**, select any log category you need.
88
88
1. In **Destination details**, check **Archive to a storage account**.
@@ -163,19 +163,19 @@ To view the resource logs, follow these steps:
163
163
164
164
1. Select `Logs` in your target Log Analytics.
165
165
166
-
:::image type="content" alt-text="Log Analytics menu item" source="./media/howto-troubleshoot-diagnostic-logs/log-analytics-menu-item.png" lightbox="./media/howto-troubleshoot-diagnostic-logs/log-analytics-menu-item.png":::
166
+
:::image type="content" alt-text="Screenshot showing the Log Analytics menu item." source="./media/howto-troubleshoot-diagnostic-logs/log-analytics-menu-item.png" lightbox="./media/howto-troubleshoot-diagnostic-logs/log-analytics-menu-item.png":::
167
167
168
168
1. Enter `WebPubSubConnectivity`, `WebPubSubMessaging` or `WebPubSubHttpRequest`, and then select the time range to query the log. For advanced queries, see [Get started with Log Analytics in Azure Monitor](../azure-monitor/logs/log-analytics-tutorial.md).
169
169
170
-
:::image type="content" alt-text="Query log in Log Analytics" source="./media/howto-troubleshoot-diagnostic-logs/query-log-in-log-analytics.png" lightbox="./media/howto-troubleshoot-diagnostic-logs/query-log-in-log-analytics.png":::
170
+
:::image type="content" alt-text="Screenshot showing the Query log in Log Analytics." source="./media/howto-troubleshoot-diagnostic-logs/query-log-in-log-analytics.png" lightbox="./media/howto-troubleshoot-diagnostic-logs/query-log-in-log-analytics.png":::
171
171
172
172
To use a sample query for SignalR service, follow the steps below.
173
173
174
174
1. Select `Logs` in your target Log Analytics.
175
175
1. Select `Queries` to open query explorer.
176
176
1. Select `Resource type` to group sample queries in resource type.
177
177
1. Select `Run` to run the script.
178
-
:::image type="content" alt-text="Sample query in Log Analytics" source="./media/howto-troubleshoot-diagnostic-logs/log-analytics-sample-query.png" lightbox="./media/howto-troubleshoot-diagnostic-logs/log-analytics-sample-query.png":::
178
+
:::image type="content" alt-text="Screenshot showing the sample query in Log Analytics." source="./media/howto-troubleshoot-diagnostic-logs/log-analytics-sample-query.png" lightbox="./media/howto-troubleshoot-diagnostic-logs/log-analytics-sample-query.png":::
179
179
180
180
Archive log columns include elements listed in the following table.
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/howto-use-managed-identity.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ To set up a managed identity in the Azure portal, you'll first create an Azure W
25
25
26
26
3. On the **System assigned** tab, switch **Status** to **On**. Select **Save**.
27
27
28
-
:::image type="content" source="media/howto-use-managed-identity/system-identity-portal.png" alt-text="Add a system-assigned identity in the portal":::
28
+
:::image type="content" source="media/howto-use-managed-identity/system-identity-portal.png" alt-text="Screenshot showing Add a system-assigned identity in the portal.":::
29
29
30
30
## Add a user-assigned identity
31
31
@@ -41,7 +41,7 @@ Creating an Azure Web PubSub Service instance with a user-assigned identity requ
41
41
42
42
5. Search for the identity that you created earlier and selects it. Select **Add**.
43
43
44
-
:::image type="content" source="media/howto-use-managed-identity/user-identity-portal.png" alt-text="Add a user-assigned identity in the portal":::
44
+
:::image type="content" source="media/howto-use-managed-identity/user-identity-portal.png" alt-text="Screenshot showing Add a user-assigned identity in the portal.":::
45
45
46
46
## Use a managed identity in client events scenarios
47
47
@@ -53,7 +53,7 @@ Azure Web PubSub Service is a fully managed service, so you can't use a managed
53
53
54
54
2. Navigate to the rule and switch on the **Authentication**.
:::image type="content" source="media/howto-use-managed-identity/msi-settings.png" alt-text="Screenshot showing the msi-setting.":::
57
57
58
58
3. Select application. The application ID will become the `aud` claim in the obtained access token, which can be used as a part of validation in your event handler. You can choose one of the following:
0 commit comments