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/network-observability-overview.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,8 +54,6 @@ When the Network Observability add-on is enabled, it allows for the collection a
54
54
55
55
* Pod level metrics aren't supported.
56
56
57
-
* The deployment of the Network Observability add-on on Mariner 1.0 is currently unsupported.
58
-
59
57
## Scale
60
58
61
59
Certain scale limitations apply when you use Azure managed Prometheus and Grafana. For more information, see [Scrape Prometheus metrics at scale in Azure Monitor](/azure/azure-monitor/essentials/prometheus-metrics-scrape-scale)
@@ -68,3 +66,4 @@ Certain scale limitations apply when you use Azure managed Prometheus and Grafan
68
66
69
67
- To create an AKS cluster with Network Observability and BYO Prometheus and Grafana, see [Setup Network Observability for Azure Kubernetes Service (AKS) BYO Prometheus and Grafana](network-observability-byo-cli.md).
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-tutorial-functions-getting-started.md
+49-62Lines changed: 49 additions & 62 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,20 +58,14 @@ The new project is created:
58
58
59
59
<!--  -->
60
60
61
-
### Install necessary NuGet packages
61
+
### Install the necessary NuGet package
62
62
63
-
You need to install two NuGet packages:
63
+
You'll need to install `Microsoft.Azure.WebJobs.Extensions.Redis`, the NuGet package for the Redis extension that allows Redis keyspace notifications to be used as triggers in Azure Functions.
64
64
65
-
1.[StackExchange.Redis](https://www.nuget.org/packages/StackExchange.Redis/), which is the primary .NET client for Redis.
66
-
67
-
1.`Microsoft.Azure.WebJobs.Extensions.Redis`, which is the extension that allows Redis keyspace notifications to be used as triggers in Azure Functions.
68
-
69
-
Install these packages by going to the **Terminal** tab in VS Code and entering the following commands:
65
+
Install this package by going to the **Terminal** tab in VS Code and entering the following command:
This tutorial shows multiple different ways to trigger on Redis activity:
171
141
172
142
1._PubSubTrigger_, which is triggered when activity is published to the pub/sub channel named `pubsubTest`
173
143
@@ -177,13 +147,24 @@ This tutorial shows multiple different triggers:
177
147
178
148
1._ListTrigger_, which looks for changes to the list `listTest`
179
149
180
-
1._ListMultipleTrigger_, which looks for changes to list `listTest1` and `listTest2`
181
-
182
150
1._StreamTrigger_, which looks for changes to the stream `streamTest`
183
151
184
-
1._StreamMultipleTrigger_, which looks for changes to streams `streamTest1` and `streamTest2`
152
+
### Connect to your cache
153
+
In order to trigger on Redis activity, you need to pass in the connection string of your cache instance. This information will be stored in the `local.settings.json` file that was automatically created in your folder. Using the [local settings file](../azure-functions/functions-run-local.md#local-settings) is recommended as a security best practice.
185
154
186
-
To connect to your cache, take the connection string you copied from earlier and paste to replace the value of `localhost` at the top of the file, set to `127.0.0.1:6379` by default.
155
+
To connect to your cache, add a `ConnectionStrings` section in the `local.settings.json` file and add your connection string using the parameter `redisConnectionString`. It should look like this:
@@ -199,12 +180,12 @@ To test the trigger functionality, try creating and deleting the _keyspaceTest_
199
180
200
181
After it's open, try the following commands:
201
182
202
-
- SET keyspaceTest 1
203
-
- SET keyspaceTest 2
204
-
- DEL keyspaceTest
205
-
- PUBLISH pubsubTest testMessage
206
-
- LPUSH listTest test
207
-
- XADD streamTest * name Clippy
183
+
-`SET keyspaceTest 1`
184
+
-`SET keyspaceTest 2`
185
+
-`DEL keyspaceTest`
186
+
-`PUBLISH pubsubTest testMessage`
187
+
-`LPUSH listTest test`
188
+
-`XADD streamTest * name Clippy`
208
189
209
190
<!--  -->
210
191
@@ -241,7 +222,13 @@ Wait a few minutes for the new Function App to be created. It appears in the dro
241
222
242
223
The app builds and starts deploying. You can track progress in the **Output Window**.
243
224
244
-
Once deployment is complete, open your Function App in the Azure portal and select **Log Stream** from the Resource menu. Wait for log analytics to connect, and then use the Redis console to activate any of the triggers. You should see the triggers being logged here.
225
+
### Add connection string information
226
+
227
+
Navigate to your new Function App in the Azure portal and select the **Configuration** blade from the Resource menu. You'll notice that your application settings have automatically been added to the Function App. For security, however, the connection string information in your `local.settings.json` file is not automatically added. Select **New connection string** and enter `redisConnectionString` as the Name, and your connection string as the Value. Set Type to _Custom_, and select **Ok** to close the menu and then **Save** on the Configuration page to confirm. The functions app will restart with the new connection string information.
228
+
229
+
### Test your triggers
230
+
231
+
Once deployment is complete and the connection string information added, open your Function App in the Azure portal and select **Log Stream** from the Resource menu. Wait for log analytics to connect, and then use the Redis console to activate any of the triggers. You should see the triggers being logged here.
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/bicep/bicep-functions-string.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
@@ -143,7 +143,7 @@ The output from the preceding example with the default values is:
143
143
144
144
`concat(arg1, arg2, arg3, ...)`
145
145
146
-
Combines multiple string values and returns the concatenated string, or combines multiple arrays and returns the concatenated array. Instead of using the `concat` function, use string interpolation, except in certain cases involving[multi-line strings](../bicep/data-types.md#multi-line-strings). For more information about combining multiple arrays, see [concat](./bicep-functions-array.md#concat).
146
+
Combines multiple string values and returns the concatenated string, or combines multiple arrays and returns the concatenated array. To improve readability, use [string interpolation](./data-types.md#strings) instead of the `concat()` function. However, in some cases such as string replacement in[multi-line strings](../bicep/data-types.md#multi-line-strings), you may need to fall back on using the `concat()` function or the [`replace()` function](#replace).
Interpolation is not currently supported in multi-line strings. The following example shows a comparison between using interpolation and using the `concat` function.
181
+
Interpolation is not currently supported in multi-line strings. The following example shows a comparison between using interpolation and using the `concat()` function.
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/templates/template-functions-string.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,8 @@ The output from the preceding example with the default values is:
150
150
151
151
Combines multiple string values and returns the concatenated string, or combines multiple arrays and returns the concatenated array.
152
152
153
-
In Bicep, use [string interpolation](../bicep/data-types.md#strings) instead of the [`concat`](../bicep/bicep-functions-string.md#concat) function, except in certain cases involving [multi-line strings](../bicep/data-types.md#multi-line-strings).
153
+
In Bicep, use [string interpolation](../bicep/data-types.md#strings) instead of the [`concat()`](../bicep/bicep-functions-string.md#concat) function to improve readability. However, in some cases such as string replacement in [multi-line strings](../bicep/data-types.md#multi-line-strings), you may need to fall back on using the [`concat()`](../bicep/bicep-functions-string.md#concat) function or the [`replace()` function](../bicep/bicep-functions-string.md#replace).
| Go |[Azure SDK for Go](https://github.com/Azure/azure-sdk-for-go)||[Go samples](https://github.com/Azure-Samples/azure-sdk-for-go-samples/tree/main/sdk/resourcemanager/eventgrid)|
> For MQTT messaging, you can use your favorite MQTT SDK. Currently Azure Event Grid doesn't provide data plane SDK for MQTT.
31
+
26
32
The data plane SDKs enable you to post events to topics by taking care of authenticating, forming the event, and asynchronously posting to the specified endpoint. They also enable you to consume first party events. Currently, the following SDKs are available:
0 commit comments