Sumo Logic, Inc. operates as a cloud-based machine data analytics company. Its solutions include log management, AWS monitoring, Azure management, cloud monitoring and GCP management.
SUMO is currently 10% of the market cap of SPLK and DDOG
What they do explained to a non-tech person:
Sumologic and services like them(Splunk/Datadog) take metrics and log files from your servers, and using complex rules they or you setup, tell you information about how your companies infrastructure is working. They can highlight errors happening, bottlenecks that are causing client issues/costing you money, alert on nightmares about to happen, etc.
It's akin to a real time view of your companies IT health, just like a financial report is a real time view of your companies business health. If your company can afford it, it's highly recommend to use one of the above, or something like them. They turn raw data into usable business data.
Compiled feedback from users:
"We like Sumo, our teams enjoy using it. Sharing of dashboards with links and with the Org makes data sharing and solving issues easier. Plus the many different ways that you can collect data into Sumo is great. They also recently released a terraform provider for it as well. There is also a fluentd plugin for it. Generally we ingest all of our applications logs into and our teams work well together. Ingest budgets have made keeping budgets under control. We have many alerts and monitoring setup from the scheduled queries that go to our VictorOps app to get sorted out to what teams they should go to"
"As someone who has rolled out both, Sumo had more ease of use for the majority of people. The language is more sql like than the elk stack and is less complex to do advanced filtering"
"We migrated from EFK stack to Sumo and devs like Sumo query language much more. Everyone hated Kibana. We now send all of our Kubernetes logs to Sumo via Fluentd. The delay is small, Ive noticed it being like 1-3 minutes sometimes when you first set up a collector. The big positives I think are the email alerts, the query language itself, and the cool dashboard you can build. The cons are that the price sucks and weve had to throttle our nonprod logs before. They are also still kinda new to metrics though so its not as refined as their logging solution."
"Sumo has been pretty solid for us for teams that don't really plan ahead for their observability needs and would rather throw all the data in a big pile and work out what is important later. Being able to throw hilariously complex parsing queries at them has been super useful there. It is, however, very expensive (and that's with some good partnership deals with them already). I also have a mixed relationship with their log alerting system, it's been very useful for teams to be able to self-service alerts but it's also pretty brittle (as are almost all log-based alerts)."
Disclaimer: This is not financial advice.
SUMO is currently 10% of the market cap of SPLK and DDOG
What they do explained to a non-tech person:
Sumologic and services like them(Splunk/Datadog) take metrics and log files from your servers, and using complex rules they or you setup, tell you information about how your companies infrastructure is working. They can highlight errors happening, bottlenecks that are causing client issues/costing you money, alert on nightmares about to happen, etc.
It's akin to a real time view of your companies IT health, just like a financial report is a real time view of your companies business health. If your company can afford it, it's highly recommend to use one of the above, or something like them. They turn raw data into usable business data.
Compiled feedback from users:
"We like Sumo, our teams enjoy using it. Sharing of dashboards with links and with the Org makes data sharing and solving issues easier. Plus the many different ways that you can collect data into Sumo is great. They also recently released a terraform provider for it as well. There is also a fluentd plugin for it. Generally we ingest all of our applications logs into and our teams work well together. Ingest budgets have made keeping budgets under control. We have many alerts and monitoring setup from the scheduled queries that go to our VictorOps app to get sorted out to what teams they should go to"
"As someone who has rolled out both, Sumo had more ease of use for the majority of people. The language is more sql like than the elk stack and is less complex to do advanced filtering"
"We migrated from EFK stack to Sumo and devs like Sumo query language much more. Everyone hated Kibana. We now send all of our Kubernetes logs to Sumo via Fluentd. The delay is small, Ive noticed it being like 1-3 minutes sometimes when you first set up a collector. The big positives I think are the email alerts, the query language itself, and the cool dashboard you can build. The cons are that the price sucks and weve had to throttle our nonprod logs before. They are also still kinda new to metrics though so its not as refined as their logging solution."
"Sumo has been pretty solid for us for teams that don't really plan ahead for their observability needs and would rather throw all the data in a big pile and work out what is important later. Being able to throw hilariously complex parsing queries at them has been super useful there. It is, however, very expensive (and that's with some good partnership deals with them already). I also have a mixed relationship with their log alerting system, it's been very useful for teams to be able to self-service alerts but it's also pretty brittle (as are almost all log-based alerts)."
Disclaimer: This is not financial advice.