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/aks/concepts-security.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
@@ -130,7 +130,7 @@ To limit network traffic between pods in your cluster, AKS offers support for [K
130
130
131
131
## Application Security
132
132
133
-
To protect pods running on AKS leverage [Azure Defender for Kubernetes][azure-defender-for-kubernetes] to detect and restrict cyber attacks against your applications running in your pods. Run continual scanning to detect drift in the vulnerability state of your application and implement a "blue/green/canary" process to patch and replace the vulnerable images.
133
+
To protect pods running on AKS leverage [Microsoft Defender for Kubernetes][azure-defender-for-kubernetes] to detect and restrict cyber attacks against your applications running in your pods. Run continual scanning to detect drift in the vulnerability state of your application and implement a "blue/green/canary" process to patch and replace the vulnerable images.
Copy file name to clipboardExpand all lines: articles/azure-monitor/logs/logicapp-flow-connector.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
@@ -16,7 +16,7 @@ For example, you can create a logic app to use Azure Monitor log data in an emai
16
16
17
17
## Connector limits
18
18
The Azure Monitor Logs connector has these limits:
19
-
* Max query response size ~16.7 MB MB (16 MiB). Connector infrastructure dictates that limit is set lower than query API limit
19
+
* Max query response size ~16.7 MB (16 MiB). Connector infrastructure dictates that limit is set lower than query API limit
20
20
* Max number of records: 500,000
21
21
* Max query timeout 110 second
22
22
* Chart visualizations could be available in Logs page and missing in the connector since the connector and Logs page don't use the same charting libraries currently
Copy file name to clipboardExpand all lines: articles/azure-monitor/logs/logs-data-export.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
@@ -69,7 +69,7 @@ Log Analytics workspace data export continuously exports data from a Log Analyti
69
69
- West US 2
70
70
71
71
## Data completeness
72
-
Data export will continue to retry sending data for up to 30 minutes if the destination is unavailable. If it's still unavailable after 30 minutes, data will be discarded until the destination becomes available.
72
+
Data export is optimized for moving large data volume to your destinations and in certain retry conditions, can include a fraction of duplicated records. The export operation to your destination could fail when ingress limits are reached, see details under [Create or update data export rule](#create-or-update-data-export-rule). Export continues to retry for up to 30 minutes and if destination is unavailable to accept data, data will be discarded until the destination becomes available.
73
73
74
74
## Cost
75
75
Currently, there are no additional charges for the data export feature. Pricing for data export will be announced in the future and a notice period provided prior to the start of billing. If you choose to continue using data export after the notice period, you will be billed at the applicable rate.
1. Remove `extensionBundle` section in`host.json` to enable install specific extension package in next step. Or simply make host json as simple a below.
71
+
> [!NOTE]
72
+
> The step will be optional when [Extension bundles](/azure/azure-functions/functions-bindings-register#extension-bundles) are supported.
72
73
73
-
```json
74
-
{
74
+
a. Remove `extensionBundle` section in`host.json` to enable install specific extension package in next step. Or simply make host json as simple a below.
75
+
```json
76
+
{
75
77
"version": "2.0"
76
-
}
77
-
```
78
-
79
-
1. Run command to install specific functionextension package.
3. Add the client single page `index.html`in the project root folder and copy content as below.
284
+
6. Add the client single page `index.html`in the project root folder and copy content as below.
274
285
```html
275
286
<html>
276
287
<body>
@@ -384,7 +395,7 @@ Use the following commands to create these items.
384
395
385
396
## Configure the Web PubSub service `Event Handler`
386
397
387
-
In this sample, we're using `WebPubSubTrigger` to listen to service upstream message requests. So Web PubSub need to know the function's endpoint information in order to send target client requests. And Azure Function App requires a system key for security regarding extension-specific webhook methods. In the previous step after we deployed the Function App with `message` functions, we're able to get the system key.
398
+
In this sample, we're using `WebPubSubTrigger` to listen to service upstream requests. So Web PubSub need to know the function's endpoint information in order to send target client requests. And Azure Function App requires a system key for security regarding extension-specific webhook methods. In the previous step after we deployed the Function App with `message` functions, we're able to get the system key.
388
399
389
400
Go to **Azure portal** -> Find your Function App resource ->**App keys** ->**System keys** ->**`webpubsub_extension`**. Copy out the value as `<APP_KEY>`.
0 commit comments