We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As reported in #2149 when importing certain metrics like azure_cosmos_db_data_usage the values continuously cycle from real value to 0.
azure_cosmos_db_data_usage
The value should be consistently showing the highest value on every point.
Value will cycle from 0 to real value.
...
Resource Discovery, Scraper
promitor-resource-discovery: 0.8.1 (helm release), 0.8.0 (container) promitor-scraper: 2.9.0 (helm release), 2.8.0 (container)
Configuration:
metricDefaults: aggregation: interval: 00:05:00 scraping: schedule: "* * * * *" metrics: - name: azure_cosmos_db_data_usage description: Total data usage reported at 5 minutes granularity resourceType: CosmosDb azureMetricConfiguration: metricName: DataUsage aggregation: type: Total
No response
Microsoft Azure
daniel.ferreira@anova.com
The text was updated successfully, but these errors were encountered:
tomkerkhove
No branches or pull requests
Report
As reported in #2149 when importing certain metrics like
azure_cosmos_db_data_usage
the values continuously cycle from real value to 0.Expected Behavior
The value should be consistently showing the highest value on every point.
Actual Behavior
Value will cycle from 0 to real value.
Steps to Reproduce the Problem
...
Component
Resource Discovery, Scraper
Version
promitor-resource-discovery: 0.8.1 (helm release), 0.8.0 (container) promitor-scraper: 2.9.0 (helm release), 2.8.0 (container)
Configuration
Configuration:
Logs
No response
Platform
Microsoft Azure
Contact Details
daniel.ferreira@anova.com
The text was updated successfully, but these errors were encountered: