Sumo Logic

Sumo logic is very flexible and easy to integrate with different cloud providers. But it's specifically easy to work with AWS.
I had to create an IAM user and provide the credentials to sumo logic collectors which started pulling in data from S3 buckets immediately.
Option to generate variety of Dashboards from real-time streaming data.

I didn't like the tabular interface. you have to scroll all the way to the right to find your tabs.
It could be have been made more user friendly.

FER Creation , dashboards are most impactful for us. Product is not very much esy to use (need some skills).
Integration with our business process are not easy , it takes some time..but once we understands about sumologic features
it gave us a major relief in application log analysis. One word excellent tool but if we know how to use it.

It's not user firendly, need some study before working.Especially the costing of frequent/infrequent/contimuous tier.
Integration is bit difficult , but our folks worked together to integrate sumologic for pur business needs.
The major drawback is it's support , currently there is no support number we need to send mail only & the support team
works in pacific timezone which is not suitable for indian time like us. For a support case it takes around 2 weeks to close.

It's a easy product to store logs Is I really love the speed and really functional and handy

Is difficult to control the size of the stored logs and the bill will be skyrocket

There are user guides at-hand for doing data searches, following best practices. You can quickly access these guides and find what you're looking for in gathering specific information for the data fed to the system. There are also many awesome options for taking data found in your log dive and putting it together to become more useful information (such as seeing how many times a specific event occurred in a specific time frame, etc).

The way data is stored and retrieved is not intuitive: key words for items allow for a faster search than specifically picking out the exact value of a parameter you're looking for. For example, you know for the purposes of your search that abc="123"; however, searching for that exact thing will take longer to search for then simply searching for "123" ... which will also find values of "123" for parameters, def, ghi, and jkl if they exist. I only want to find values of "123" for parameter abc. ... yet for some reason, there's no good way to retrieve that information, even though we've fed the data to the system, and it exists. This is more of a problem if you actually need to search your data for specifics on a regular basis; if you're just managing the data and only searching for real time data, it may not be quite as important.