3 ms·
ES revenue can cover a lot of devs. But rephrasing: is ES the logging and visibility solution they are betting on, or is ES an 'ok to be 2nd for folks insistin
by lmeyerov 7y ago
ES revenue can cover a lot of devs. But rephrasing: is ES the logging and visibility solution they are betting on, or is ES an 'ok to be 2nd for folks insisting on ES' and they plan to win with other cloud-native log/doc analytics tooling?
(Their crocodile smile on ethical open source practices through better operational excellence reads even thinner when seeing stuff like this tho.)
- time0ut 7y agoThey've definitely been positioning it as the preferred solution. Our SA steered us towards it as a general search solution over their seemingly abandoned cloud search offering. The (also abandoned) AWS landing zone has an addon to stand up an ELK stack for you and no alternative afaik.
- lmeyerov 7y agoReally not obvious to me... just as MS released internal Kusto as a product, and Google did BigQuery, I've been curious if some internal more integrated Amazon tool would surface. E.g., see the direction of CloudWatch to go from metrics queries to log queries (https://aws.amazon.com/about-aws/whats-new/2019/07/cloudwatch-logs-insights-adds-cross-log-group-querying/ https://aws.amazon.com/about-aws/whats-new/2019/07/cloudwatc...) and how GuardDuty is marching towards a modern SIEM. What the cloud vendors can do vs. splunk/elk/cisco makes it feel more like a "when" not "if". Zero judgement here on technical quality, this is just the nature of big tech co's. Do most AWS teams use ES, or something else? Is CloudWatch Insights on a scaling & parity path?