Sumo Logic

Sumo Logic is used mostly for analysis in gaps where other monitoring tools fall short. Specifically, log aggregation and even more importantly than the aggregation is that it uses intelligent (and customizable) heuristics to analyze logs for specific event information and sorting.

We use sumo logic primarily for historical analysis but it is very reliable and customizable. For example, for errors that show symptoms directly in their log files (which we already piped to sumo logic for historical analysis) we have used this to generate alerts. This is ideal as log errors often occur before a service fully crashes and has reduced our response time to these types of incidents.

Finally, we have turned some of these into dashboards for certain business users. I don't think there is much helpful use to technical needs, but it can help quickly satisfy business users by providing simple and quick insights into the IT infrastructure. This is a common type of request for internal IT and it is nice to be able to actually fulfill those tickets instead of declining them (without a good tool, it might not be practical to fulfill such small impact requests).

Sumo logic is being used as a single source of log aggregation for multiple system types from Windows, Linux, Networking, Mainframe, etc. This allows cross OS/cross system searches for specific items. This allows our IT security team to research issues quickly. This also allows us to limit the amount of disk space used to store logs on internal systems. We can build custom reporting to track issues or changes that can be shared with teams and management without allowing direct access to the systems involved.

Sumo Logic is being used across our company. Our logs are first published to CloudWatch, and then pushed over to Sumo Logic for analysis and debugging. Each log is tagged with a session id that we can use to track API calls across services. We use the logs to verify customer issues, and it lets us see which APIs, and therefore which team to reach out to so we can solve a given issue.

We use Sumologic for analyzing and checking logs. Mostly if any issues or customer-reported errors we rely on sumologic logs. We use [it] in all our environments. It helps my day-to-day work in troubleshooting issues. We also have graphs, charts for regular monitors. It is used across all departments in our organization.

Sumo Logic was being used by developers, system engineers, management, and InfoSec as a primary log aggregation tool. It was replacing the Splunk deployment in our enterprise because it was cheaper, hosted by Sumo Logic, and helped bring larger visibility to the enterprise (as we were able to ingest larger amounts of logs than we had before). As a result, many developer teams that did not initially have the insight into their applications were able to get instant access to how things were running on their systems.