From 2c5b79567ca4d28e70df9fd53d0ef15717a97ee1 Mon Sep 17 00:00:00 2001 From: Jorge Turrado Ferrero Date: Tue, 12 Oct 2021 08:12:58 +0200 Subject: [PATCH] Update metric names where the names are explicitly shown (#550) --- content/docs/2.5/scalers/azure-storage-blob.md | 2 +- content/docs/2.5/scalers/mongodb.md | 4 ++-- content/docs/2.5/scalers/mssql.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/2.5/scalers/azure-storage-blob.md b/content/docs/2.5/scalers/azure-storage-blob.md index b269176db..c87c7dd96 100644 --- a/content/docs/2.5/scalers/azure-storage-blob.md +++ b/content/docs/2.5/scalers/azure-storage-blob.md @@ -38,7 +38,7 @@ triggers: When `cloud` is set to `Private`, the `endpointSuffix` parameter is required. Otherwise, it is automatically generated based on the cloud environment. `endpointSuffix` represents the storage blob endpoint suffix of the cloud environment that the blob belongs to, e.g. `blob.core.cloudapi.de` for `AzureGermanCloud`. -You can also optionally assign a name to the metric using the `metricName` value. If not specified, the `metricName` will be generated automatically based on of the `blobContainerName`, `blobPrefix` and `blobDelimiter`. For example: **azure-blob-functions-blob-myprefix-example**. If using more than one trigger it is required that all `metricName`(s) be unique. The value will be prefixed with `azure-blob-`. +You can also optionally assign a name to the metric using the `metricName` value. If not specified, the `metricName` will be generated automatically based on the trigger index, `blobContainerName`, `blobPrefix` and `blobDelimiter`. For example: **s0-azure-blob-functions-blob-myprefix-example**. The value will be prefixed with `s{triggerIndex}-azure-blob-`. ### Authentication Parameters diff --git a/content/docs/2.5/scalers/mongodb.md b/content/docs/2.5/scalers/mongodb.md index bcd2f0550..47007036c 100644 --- a/content/docs/2.5/scalers/mongodb.md +++ b/content/docs/2.5/scalers/mongodb.md @@ -55,7 +55,7 @@ triggers: metricName: "global-metric" ``` ->**NOTE:** If **metricName** is not set, then one is generated based on the values in trigger spec, for example: **mongodb-mongodb---test_user-test_password@xxx-27017-test-test_collection** +>**NOTE:** If **metricName** is not set, then one is generated based on trigger index and the values in trigger spec, for example: **s0-mongodb-mongodb---test_user-test_password@xxx-27017-test-test_collection** **Parameter list:** @@ -83,7 +83,7 @@ When configuring with a connection string, you can use this URL format: mongodb://:@mongodb-svc..svc.cluster.local:27017/ ``` -You can also optionally assign a name to the metric using the `metricName` value. If not specified, the `metricName` will be generated automatically based on masked version of the server hostname and collection name. For example: **mongodb-mongodb---test_user-test_password@xxx-27017-test-test_collection**. If using more than one trigger it is required that all `metricName`(s) be unique. The value will be prefixed with `mongodb-` . +You can also optionally assign a name to the metric using the `metricName` value. If not specified, the `metricName` will be generated automatically based on trigger index and masked version of the server hostname and collection name. For example: **s1-mongodb-mongodb---test_user-test_password@xxx-27017-test-test_collection**. The value will be prefixed with `s{triggerIndex}-mongodb-` . ### Authentication Parameters diff --git a/content/docs/2.5/scalers/mssql.md b/content/docs/2.5/scalers/mssql.md index e88abee6e..feeafca21 100644 --- a/content/docs/2.5/scalers/mssql.md +++ b/content/docs/2.5/scalers/mssql.md @@ -68,7 +68,7 @@ Or the more traditional ADO format: Server=example.database.windows.net;Port=1433;Database=AdventureWorks;Persist Security Info=False;User ID=user1;Password=Password#1;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30; ``` -You can also optionally assign a name to the metric using the `metricName` value. If not specified, the `metricName` will be generated automatically based on the `database` value (if specified), or the `host` value, or will be in the form `mssql-{sha256hash}` where `{sha256hash}` is a SHA-256 hash of the connection string. +You can also optionally assign a name to the metric using the `metricName` value. If not specified, the `metricName` will be generated automatically based on trigger index and the `database` value (if specified), or the `host` value, or will be in the form `s{triggerIndex}-mssql-{sha256hash}` where `{sha256hash}` is a SHA-256 hash of the connection string. ### Authentication parameters