> I can find someone on LinkedIn who can manage my Azure logging infrastructure are infinitely greater than finding someone who has experience with my custom lo

> I can find someone on LinkedIn who can manage my Azure logging infrastructure are infinitely greater than finding someone who has experience with my custom logger's private repository Why not do something standard with no platform lock-in? We do structured logging and push them to an Elastic stack with fluentd. For now we use an Elastic we deployed on a Linux VM but 1) we can move at any time, either from cloud provider, or stop using Elastic if we want to, and 2) we can probably find more people who can manage that than whatever Azure solution you’re using I see no reason for getting locked in for something like logs. We actually did that with AWS Cloudwatch at some point and it was a horrible experience