-
-
Notifications
You must be signed in to change notification settings - Fork 94
Intermittent fatal errors: InvalidOperationException: Sequence contains no matching element #2331
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
Comments
Thanks for the report. Are you willing to contribute a fix? |
We would be willing to contribute (I'm at Axon, and we have contributed before). We just wanted to get your take on what you think is happening and confirm that you think it's a bug, as opposed to normal, expected error due to a misconfiguration or misuse. |
@tomkerkhove let me know your initial thoughts. I will schedule someone from my team to dig into it with any direction you provide. You already know @locmai. Others on my team could investigate it as well. |
Please give me some time as I maintain more than just Promitor so I cannot guarantee a response within 1-2 days :) I think the exception is fairly clear and the |
We will start looking into this over the next two weeks to see if we can improve the handling in this method. |
Report
We have some metrics that scrape fine >99% of the time, but encounter an FTL error in the scraper code a few times per day for some reason. It's just a couple failed scrapes here and there, but it would be nice to know what condition causes this, and hopefully there is a way to improve it.
Example configuration that works >99% of the time
Here's the error that gets logged when the scrape fails:
Expected Behavior
Properly defined metrics should work consistently when Azure Monitor itself is in good condition.
Actual Behavior
Properly defined metrics experience intermittent fatal errors on scrapes, just a few per day always.
Steps to Reproduce the Problem
Component
Scraper
Version
v2.9.1
Configuration
Configuration:
Logs
Platform
Microsoft Azure
Contact Details
No response
The text was updated successfully, but these errors were encountered: