Extreme increase in traces produced by Azure Function leading to large consumption
Veronika Miklinova
0
Reputation points
Our node.js Function App started producing extreme amount of traces (1500 per second). There was no change in the function from our side around that moment.
The function is triggered once every minute so the number or requests does not correspond to the number of traces. There are no errors and the function works so it generated a huge expense without alerting us that something is wrong.
We stopped the function now but we need to find out what happened.
Sign in to answer