Hacker News Reader

I had Azure AKS monitoring turned on for a minuscule, essentially unused hobby project. After about four months the monitoring costs suddenly exploded from about $4/mo to about $4k/mo.

No idea what happened and MSFT support couldn't tell me what was happening because at more than $100/day burn rate on a hobby project I started deleting everything connected with the effort as fast as possible.

All I know is my AKS wasn't exploding. Services were still responsive and acting normally in their minuscule cluster, this was just a logging cost explosion.

Also billing alerts are your friend.

That might be okay, say you enable all for 10 - 20 seconds, such that all traces are sampled, logs logged, etc, and then it ramps down.

Yeah got burned by that once. Fortunately I had billing alerts in place so we found it quick…

This is the default monitoring which comes with AKS setup right?

I'm not sure....I don't think it was turned on by default for AKS. I can do some digging if you want.