Sumo Logic Security Reviews

I use it for the log monitoring of our legacy site. We typically monitor the event timestamps.

The tool has key features like operability. It will alert the admins whenever a device is onboarded.

From the network segmentation side, there is some discrepancy in log onboarding. The tool needs to improve direct API integrations, login integration, native login integration, etc. 

I have been working with the product for three years. 

I would rate the tool's stability a nine point five out of ten. 

I would rate the product's scalability a nine out of ten. 

The support replies to us back within 24 hours of opening a ticket. 

Positive

The tool's setup is simple and straightforward.  A three-member team manages the solution. 

I would rate the solution a nine out of ten. 

We mainly use the solution to take advantage of the debugging logs and application logs, which are the production systems that we have. All of these are running these Sumo Logic agents. They keep communicating with the logs and are pushing to the Sumo Logic servers. Basically, we use it for our application debugging. 

We also push the balance of our logs to Sumo Logic. That is for our workarounds. It helps us to get to know the health of our application from the load balancer point of view. We pull for certain error messages within the logs, let's say, for example, exceptions, or errors, etc. We use certain patterns that we want to be highlighted for notification purposes. These are running continuously and whenever certain text patterns are found and are beyond a certain threshold, we get notified so that we can take some corrective actions.

There are a lot of things we like about this product. 

One is the log aggregation. It basically gives a list of matching patterns on most of the logs. When dealing with something like live error messages etc., you can group by similarities.  That way it is very easy to know where things are in real-time. It has helped us in terms of doing a top-down debugging. If, for example, you see a certain error message or an exception, then you double click to see where exactly it has affected the system. That way, at every stage you are able to go one level deeper until you find the root cause, through the logs or by other means. This is something which I find it really helpful. There are other ways within a window you can search as well. You can find out what happened one or two days before or one or two minutes before this message. It helps you follow a trail of events that will lead you to a particular state.

Users can also do a comparison with regard to the filing. Let's say, for example, you see a certain error come up today, and if you are interested in how was it yesterday or the day before, or maybe 17 days ago, you can take a look. This is one of the features that I found really helpful. 

The solution offers capture host metrics as well. Basically it could be the RAM utilization, CPU, or pretty much everything around the host, including the health of the host. That also comes in handy when we are debugging.

There isn't anything in particular that stands out that I would say is lacking or needs adjustments. For us, the solution offers everything we need.

If you look at some of the other offerings right now that are available in the market, they do offer APM as well as the product they're offering. I believe Sumo Logic is not there yet. So that's something which I would love to see. If Sumo could come up with the feature and then make it as a part of the offering that would be ideal.

The pricing could be more competitive. Sumo Logic bills based on the amount of data that you ingest into their platform. There are times that some of the data is not critical. You don't want to be charged at the same level for the extra data that isn't critical, but you will be.

We recently started using the solution. We started originally sometime in October or November of 2019. It's been maybe eight to ten months since we began.

The solution is quite stable. 

We have had barely any occasions where we witnessed delays. This may have happened once or twice. That is, of course, over a period of months. We started evaluating them in October, but we signed to use them sometime in January. Since January we have been developing customers for them. In the past four or five months that we've been using the solution, only once or twice did we see some kind of a lag in the logs getting pushed. I believe that is an understandable and typical amount of time. If we have had to reach out to their support only two times in about five months, I don't think that's bad.

We've never had any issues with developing scalability. Whatever that we were pushing, in terms of logs, they're all getting pushed and we haven't seen any scalability issues.

We've had no issues whatsoever with the level of service we've been given.

Right now, their customer success team, their version of technical support, will check in to see how we're utilizing the tool. If there's anything we're stuck on they will manage it for us. Whenever we have too many logs, and if we are exceeding our quota, they will personally reach out and check-in. They are really engaged and want to know if things are working as expected or if there at any anomalies. Due to the fact they are so attentive, if they catch anything, they will reduce certain charges so they try to protect our average rates.

The initial setup is very easy. 

In terms of the initial deployment, it's just a matter of installing the solution. It's sort-of similar to onboarding a server.

We did get help from the pre-sales team from Sumo Logic, who was helping us with the initial onboarding and procedures. We also do have their support team available to us. They're called the Customer Success Team.  

They've given us a lot of insight into the tool and they call maybe once a month to check-in. 

The solution is expensive in terms of usage. New users should be aware of that. However, for some that are worried about down-time on their applications, if you can't target, then it makes sense to invest money in a tool like this, and with Sumo especially,

We're just a customer.

It's a good tool. It has helped us, and there's a whole lot of features included. 

For new businesses considering using the solution, if you are strictly or directly only looking towards the cost then it might not be justified, because stability is something which can't be measured, or rather it's not exactly tangible. You might say that, okay, one hour of downtime results in so much of a loss in the business, and if you're effectively making use of the tool for bringing up the systems really fast, potential damage will be zero.

I'd rate the solution eight out of ten.

To rate it at a perfect ten, maybe if they offered just a few more features I'd rate it higher. 

They would also get a higher rating if they offered differential pricing to focus on super-critical logs instead of all data in aggregate. On a need basis, whenever I do a query on them, I should be charged based on that. So some kind of a differential pricing model is something that I would expect out of this platform.

Logging all operational and security events in our enterprise environment. We use Sumo Logic to monitor all the applications that we run in the Amazon AWS cloud; we use Sumo Logic to monitor the security posture of our AWS IaaS with CloudTrail, VPC flow, S3 audit, GuardDuty, and EKS services. 

Sumo Logic is a single place to retrieve intelligence without worrying about architecture and performance.

The out of the box applications were very useful for us. We also use the Threat Intelligence integration for our security monitoring.

Automation is open to user's implementation, in my case, we used to use API to correlate and orchestrate events from Sumo Logic with other platforms, and now we are using an automation platform to centralize the various integrations.

We use it for logging and alerting for cloud only applications.

We are only use it from the cloud.

We are able to diagnose problems before our customers.

• It's reliable.
• The Curry language is easy to use once you get used to it. 
• The user interface is pretty responsive. 

Therefore, it was a cost value proposition decision.

There are some API gaps that are missing.

It is usually reliable when we expect it to be. We haven't had too many outages. They announce outrages when they have them; more due to degradations when they have them. They have been more reliable than some other vendors that we are using.

We have had no issues with scaling.

We frequently reach out to tech support. We also have a technical account manager (TAM) and a customer success manager assigned to us. We have a fairly large account with them, so we generally get the responses that we need.

We have our own logging solution previously.

The integration and configuration in our AWS environment is automated. We automated it so every AMI comes ready with Sumo Logic and New Relic. Therefore, we have no issues.

We integrated with New Relic. Thus, we get alerts sometimes from Sumo Logic's logs as opposed to just native alerts when they are from CloudWatch or New Relic.

We look at ROI constantly. We put the amortized cost of Sumo Logic and New Relic right in the console that our service teams can look at. The ROI is good enough for us not to move away from Sumo Logic.

The AWS Marketplace pricing is borderline. Every annual renewal, we always contemplate if we are getting what we think we could out of it or could we do it cheaper with some other product.

I believe that we did look at another cloud-based solution, but I wasn't at the company during the evaluation process.

I would recommend to look at Sumo Logic, but also look at Datadog and Loggly. Look at some of the competitors who are also in this space.

Sumo Logic is for logging. You can use it as a centralized logging management system. You can send all your application logs to Sumo Logic, then you will receive a clear dashboard where you can see if there are any issues in you operations. It is pretty easy to troubleshoot any issues on your application using Sumo Logic.

It helps a lot because we can troubleshoot issues pretty easily. 

We can easily search for what is wrong in our application through the logs. We don't need to go through all of the logs. We just make a search on the basis on some keyword, then we will see the actual problem in Sumo Logic.

With the alerting dashboards, you can set up some patterns. Then, on these patterns, you will automatically get alerts.

Currently, it has predefined patterns that we need to set up manually. We would like to have some type of predefined setup for the logs, making the setup easier by default, such as:

• What are the total number of error logs? 
• What are the total number of hits? 
• What are the total number of misses? 
  

The stability is pretty good. I haven't seen more than two or three times when the dashboard has not been working, the logs are not available on the dashboard, or there is some latency in the logs. I always get the real-time logs on the dashboard.

The scalability is good. We have scaled from two servers to 50 servers, and it works well.

If you are enterprise level and your server size is more than ten or 15, then I would recommend to use Sumo Logic.

Initially, we used technical support because when we were new to Sumo Logic. So, we had some issues setting up dashboards. However, after a couple of hands on experiences, the product was pretty easy to use. 

The technical team is good and helped us out.

The integration and configuration of Sumo Logic in our AWS environment was easy. If you can read the documentation, then you can easily set it up.

The troubleshooting part of Sumo Logic has solved a lot, e.g., if there is any downtime on the website. So, we have reduce our downtime by a lot with Sumo Logic because we can easily troubleshoot issues.

The pricing is a little high, but for the features that we receive from Sumo Logic, it suits the price. For some small organizations, the price might be a little high.

We have used other products, like Loggly and ELK Stack.

Our log sites are huge, and Sumo Logic was a good option for the large volumes. ELK and the other options were not working well with the large volumes.

If you want to do a PoC with Sumo Logic, their documentation is very good.

The product is only on AWS. We using it on our production environment.

We use it for monitoring and alerting on application logs.

We have used it many times to find a root cause of a live issue, then fix the problem in the applications.

• The tools that they have for searching through logs.
• Doing log comparisons.
• Time shifting the logs.
• The dashboards are good.

We would like the ability to drill down into a dashboard and get into deeper levels.

Some of the operations and security team members don't think Sumo Logic does as well as Splunk in their field. Sumo Logic could possibly do more work with security teams and the operations side to bring in some additional features that Splunk has which Sumo Logic doesn't.

We put a good amount of strain on the product, and it has held up very well.

It scales very well. Our environment has several hundred applications running on it with about a 1000 hosts.

Support has been excellent. Sumo Logic's support staff is really good, both their account management staff and direct support.

The integration and configuration in the AWS environment was very easy. They published some sample code for integrating with Lambda and other technologies, and it is pretty easy to get there.

We also looked at Splunk. However, Sumo Logic was better liked by the developers. It had a more intuitive interface and a better set of tools for analyzing logs to do root cause analysis and caching. We chose the product based on the input from the developers who did the analysis.

I would recommend Sumo Logic. It is easy to use. The culture at Sumo Logic seems to be developer focused. The product is good. The developers are able to use it to get their job done quickly and easily. It fits into the developer's workload. The support is excellent.

We use it in both AWS and on-premise. It tends to work the same in both cases.

We have integrated it with Beanstalk, Lambda, and EC2, and it integrates very well. Though, they have some work to do on the containment side, at least with EC2.

We use it to keep our information database.

It provides easy visibility. I also like the shareable queries because we share a lot across groups.

Being able to join logs together across many services and servers.

There needs to be improvement on imported data which can be used within Sumo Logic to do more advanced queries.

We haven't had issues with it since I have been working with it.

The scalability fits our needs. It seems very fast and works well.

We just reach out via email if we need assistance.

I don't pay the bill. I've heard the AWS Marketplace pricing is high, but I like the value.

It was already in place when I joined the company, and we are not currently looking at any alternatives.

Reach out, see if you can get a demo on your data, and see how it fits your needs.

It works with all our main applications, so the integration with those products is pretty seamless from my standpoint.

We use the AWS version.

Our primary use case is application log tracing and monitoring. It does a good job of meeting our needs, in terms of alert monitoring.

For many of our services, we use Sumo Logic to track errors and send notifications to our Slack channel, if there are issues. Then, we have our support people monitoring this, and they can react quickly.

The key features that we have been using:

• The ability to troubleshoot production issues.
• Set up monitoring for errors. 

I would like better UI-driven functionality to create alerts and reports. Now, we have to understand the syntax, so it is a little difficult for someone to pick it up without using the manuals. If there was more of a graphical user interface, it would be beneficial.

It would be nice to have an improved ability to scroll through logs within a time frame. Right now, we can search for specific errors. However, if we want to look for "before and after" within a specific time frame, it's not easy using the tool. This would be an improvement.

We are still looking for some functionality to make the alerting and monitoring set up easier and more user-friendly.

We are sending out real-time streaming of logs from multiple applications, and we haven't had any issues with the application.

Scalability has been good for our needs. 

We have applications across the company which are using Sumo Logic. We haven't run into any scaling issues in regards to size so far.

We haven't reached out to technical support yet.

The integration was set up by us. What we did was use our deployment automation tools to send logs over to Sumo Logic. Most of this was done on our side. It would have been nice to have some out-of-the-box plugins which could have been used for this purpose.

We integrate with a lot of custom applications, mostly running on a Linux environment. What we do is we send logs from the Linux file systems over to Sumo Logic.

We have seen improvement in our operational processes.

Pricing has been cheaper than some of the competing tools, like Splunk. However, if we went to ELK Stack, which is open source, it would have been less costly, but it would have required more development from our side. It is a good balance between price and functionality.

We also looked at Kibana. 

We chose Sumo Logic because it had robust functionality. We also had a licensing agreement with the parent company.

It is a good tool for operational logging and monitoring of applications.

We are using the hosted version.