We use Sumo Logic to collect all our logs in one central location. This makes it easier for developers to search for errors in our systems. We also use it to create dashboards for stakeholders. We process large amounts of requests, sometimes millions per day, so we want to track things like successful transactions and data volume in queues. Sumo Logic dashboards help us analyze this data quickly and easily. So, so it's primarily for log aggregation and analysis.
Software and Systems Engineer at Ben Abrams Consulting
Real User
Top 10
2024-01-11T22:06:00Z
Jan 11, 2024
I led the security team for the company. We use Sumo Logic Observability for SIEM capabilities, general log storage management, scheduled searches, dashboarding, observability, and visibility. Other application and infrastructure teams, including SRE, used it mainly for logging.
Cyber Security Specialist at a tech services company with 501-1,000 employees
Real User
Top 20
2023-05-22T18:22:31Z
May 22, 2023
If you're attempting to swiftly navigate through a substantial amount of data you can expand the implementation of Sumo Logic Observability across various organizations, but it is crucial to ensure that you properly analyze all the data being ingested into it. Moreover, comprehending the cost structure and prioritizing specific logs can greatly assist in a security investigation. The manner in which you utilize it can be somewhat subjective, as it can be integrated with other security solutions. For example, I'm currently trying to examine a vast range of data and perform queries, but I'm unsure about searching for email data. Previously, I utilized it to identify particular strings within log data, but I find it somewhat challenging due to the additional effort required. Writing numerous queries consistently can be burdensome, particularly for smaller teams without a full complement of engineers to fully develop the solution. Scaling without substantial resources can be a daunting task. However, if you integrate it effectively within your environment and incorporate tools like a Security Orchestration, Automation, and Response (SOAR) system, you can automate a significant portion of the process. Nevertheless, for companies operating on a limited budget, this may present a significant challenge.
Sumo Logic Observability is widely used for log aggregation, analysis, and SIEM capabilities. It assists in monitoring data, creating dashboards, and managing log storage.
Sumo Logic Observability helps teams with logging in production, debugging with trace IDs, and performing queries across large datasets. Developers leverage centralized logs for error detection and tracking metrics like successful transactions and data volume. Security teams integrate it with SOAR systems for...
We used it for log observability – log aggregation specifically.
The product helps to monitor data and alerts when it is triggered.
We use Sumo Logic to collect all our logs in one central location. This makes it easier for developers to search for errors in our systems. We also use it to create dashboards for stakeholders. We process large amounts of requests, sometimes millions per day, so we want to track things like successful transactions and data volume in queues. Sumo Logic dashboards help us analyze this data quickly and easily. So, so it's primarily for log aggregation and analysis.
I led the security team for the company. We use Sumo Logic Observability for SIEM capabilities, general log storage management, scheduled searches, dashboarding, observability, and visibility. Other application and infrastructure teams, including SRE, used it mainly for logging.
If you're attempting to swiftly navigate through a substantial amount of data you can expand the implementation of Sumo Logic Observability across various organizations, but it is crucial to ensure that you properly analyze all the data being ingested into it. Moreover, comprehending the cost structure and prioritizing specific logs can greatly assist in a security investigation. The manner in which you utilize it can be somewhat subjective, as it can be integrated with other security solutions. For example, I'm currently trying to examine a vast range of data and perform queries, but I'm unsure about searching for email data. Previously, I utilized it to identify particular strings within log data, but I find it somewhat challenging due to the additional effort required. Writing numerous queries consistently can be burdensome, particularly for smaller teams without a full complement of engineers to fully develop the solution. Scaling without substantial resources can be a daunting task. However, if you integrate it effectively within your environment and incorporate tools like a Security Orchestration, Automation, and Response (SOAR) system, you can automate a significant portion of the process. Nevertheless, for companies operating on a limited budget, this may present a significant challenge.