I have a Azure Function (v2) that monitors a blob container and triggers on new blobs. The function was working fine until it stopped unexpectedly. We have since diagnosed the issue to being a result of the logs no longer being written (see question on MS Forums).
As I understand, an Azure Function monitors blobs directly until there are more than 10k blobs in a container (see this document). This was the case with my function - I had over 10k blobs so the logs were being monitored. I have since deleted a majority of my blobs, leaving only a few hundred in each container, include those located in the $log container (a couple thousand among all containers). My function still does not fire on new blobs, indicating that the logs are still being monitored (which are not working correctly).
My question is, how does the Function runtime decide to poll blobs directly or use logs? And how do I get the runtime to stop monitoring log files?