Bad request error in promitor scraper #1939
-
Hi Team, We are using promitor 2.1.0 version for metric collection of azure managed service. We were able to successfully get data for eventhub through auto discovery but today got below error in scaper: Can you please help to identify what this might be related to? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
That is odd, are there any other logs than this? Can you share your config please? You might want to try using v2.5 or so to ensure this is still an issue. |
Beta Was this translation helpful? Give feedback.
-
Hi @tomkerkhove , Below are the config:
azureMetadata:
We are planning to upgrade scraper and discovery in production |
Beta Was this translation helpful? Give feedback.
-
The versions is not updated yet name: Active_Connections Good for now. I'll try using discovery once the version is updated :) |
Beta Was this translation helpful? Give feedback.
The versions is not updated yet
Same config worked without promitor discovery...
azureMetadata:
subscriptionId: #############
tenantId: ############
resourceGroupName: ############
metricDefaults:
aggregation:
interval: 00:05:00
scraping:
schedule: 0 * * ? * *
metrics:
name: Active_Connections
description: "Total Active Connections for Microsoft EventHub"
resourceType: Generic
azureMetricConfiguration:
metricName: ActiveConnections
aggregation:
type: Total
resources:
resourceUri: Microsoft.EventHub/namespaces/######
[13:21:04 INF] Found value 0 for metric Active_Connections with aggregation interval 00:05:00
Good for now. I'll try using discovery once the version is updated :)