Hey everyone! My organization is shifting from NSG flow logs to VNet flow logs due to the retirement of NSG. During our tests, we've noticed that the volume of logs has skyrocketed—up by 3.3 times! This spike is quite significant in terms of both cost and operational challenges, and it's making it hard for us to fully utilize VNet flow logs. Is there a way to cut down on the volume of these logs? Any tips would be appreciated!
3 Answers
I totally get what you’re saying. We're going through a similar transition as well. Out of curiosity, how do you all manage your logs? Are you just storing them in a storage account, or do you send them to a third-party service?
Beyond adjusting storage tiers, I'm not sure there’s much you can do to reduce log volume. Have you thought about compressing the logs before moving them to cool storage? That might help save on costs in the long run.
You're not alone; I've been dealing with the same issue! It would be great if there was a way to filter the types of logs we generate with VNet flow logs. If anyone has found a solution to this, I’d love to hear about it!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures