-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
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
Batch Mode fails on Azure Firewall DataProcessed Metric #2587
Comments
Thank you for opening an issue! We rely on the community to maintain Promitor. (Learn more) Is this something you want to contribute? |
Seems like this is not particular for the Data Processed metric but more of a generic issue. Or could be to the Azure Firewall scraper scope, geting more log"
So that we jumped to this catch promitor/src/Promitor.Core.Scraping/AzureMonitorScraper.cs Lines 120 to 128 in 202e15b
promitor/src/Promitor.Integrations.AzureMonitor/AzureMonitorQueryClient.cs Lines 121 to 131 in 202e15b
|
Report
Relevant code on that path:
Somehow resourceID was not properly parsed out from metric results.
Expected Behavior
Scrape results processed and published.
Actual Behavior
Processing failed because resource ID was not attached to scrape results on this particular metric.
Steps to Reproduce the Problem
DataProcessed
metricComponent
Scraper
Version
Scraper-v2.11.2
Configuration
Configuration:
# Add your scraping configuration here
Logs
Platform
None
Contact Details
No response
The text was updated successfully, but these errors were encountered: