Skip to content

Commit 24c553b

Browse files
committed
update
1 parent 23b6d27 commit 24c553b

1 file changed

Lines changed: 0 additions & 27 deletions

File tree

articles/container-apps/functions-keda-mappings.md

Lines changed: 0 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -150,38 +150,11 @@ Use this value as the target for the total lag (sum of all partition lags) to tr
150150

151151
`metadata.lagThreshold` = `LagThreshold`
152152

153-
### Azure Cosmos DB
154-
155-
The [Azure Cosmos DB trigger](/azure/azure-functions/functions-bindings-cosmosdb-v2-trigger) doesn't map to a KEDA scaler. Use custom scaling instead.
156-
157-
The Functions trigger sets the maximum number of items received per function call. Transaction scope is preserved for stored procedures.
158-
159-
| Parameter | Functions Configuration | KEDA Configuration |
160-
|--|--|--|
161-
| **Parameter name** | `MaxItemsPerInvocation` | N/A |
162-
| **Configuration path** | Function trigger attribute | N/A |
163-
| **Default value** | 100 | N/A |
164-
165-
#### Example
166-
167-
```csharp
168-
[CosmosDBTrigger(
169-
databaseName: "ToDoItems",
170-
containerName: "Items",
171-
Connection = "CosmosDBConnection",
172-
MaxItemsPerInvocation = 100)]
173-
```
174153

175154
### HTTP trigger
176155

177156
The [HTTP trigger](/azure/azure-functions/functions-bindings-http-webhook) doesn't map to a KEDA scaler. Instead, use the Container Apps built-in HTTP scaling capabilities or external monitoring solutions.
178157

179-
| Parameter | Functions Configuration | KEDA Configuration |
180-
|--|--|--|
181-
| **Parameter name** | `maxConcurrentRequests` | N/A |
182-
| **Configuration path** | `extensions.http.maxConcurrentRequests` (host.json) | N/A |
183-
| **Default value** | 100 (Consumption), -1 (Premium/Dedicated) | N/A |
184-
185158

186159
## Related content
187160

0 commit comments

Comments
 (0)