Detailed logging without much setup.
Updated December 08, 2020
Detailed logging without much setup.
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with SolarWinds Loggly
We are using Loggly to better monitor and debug a large scale application platform that is leveraging multiple microservices. We also have it configured into our web application talking to these services. Loggly provides us detailed information across all four environments (development, QA, UAT, Production) that enables us to better analyze and consolidate activity that can be interrelated at times.
- Aggregation
- Filtering
- Detailed Information
- Configuration
- Visualization
- Organization
- It has made it easier to store all of our logs
- It has been difficult to properly filter data
- It allows us to easily integrate with our various platforms
We initially setup New Relic to monitor our servers/performance as well as look into the potential of having our servers log data into there as a "single source" of our data monitoring. However, we found that the logging needs in New Relic were not in line with the application level logging we wanted to do with our applications. We similarly looked into CloudWatch as a means of logging items since we already had our infrastructure within AWS. With CloudWatch, we found the feature set for filtering a bit more limited compared, so we decided to go with Loggly instead. We also found the initial setup with Loggly to be easier.
ROI
- Price
- Product Features
- Product Usability
The tagging features/searching were the biggest features that swayed us towards Loggly. Sometimes we needed to track logs from the same microservice type (vehicles) across our various environments (dev/test/uat/production) to look for anomalies in the data we were tracking. Most system did not have this ability or made it very difficult. With the ability to dynamically add tags to any of our log entries themselves, it gave us the power to search and view in such a manner.