Earlier quoted context omitted.
This makes a lot of sense because most of us aren't going to work with a different company for each and every part of our infrastructure. If it's super critical it be the best, I'm going to seek out the right tool for the job. If I just need to have something, at a basic level, I'd rather work with a company I already work with.
Absolutely. I think the parent poster is massively overgeneralizing that CloudWatch is only good for "hobbyist users". Nearly every product I've worked on that's utilized AWS has sent to CloudWatch, because unless they have special needs CloudWatch doesn't meet then you might as well use it because nearly every AWS product and docs are already sending their logs there by default and it's one less infrastructure compa…
It does seem like as of last week's announcement they are starting to try to fix this. I was annoyed we had to log stuff to both Cloudwatch and Splunk to try to get decent logging.