Overall Satisfaction with SolarWinds Papertrail
We use SolarWinds Papertrail for logging across a cluster of servers. Before using SolarWinds Papertrail we didn't have any easy way to aggregate logs across all of our servers. We needed a way to watch what was going on both on individual servers in addition to having cluster-wide visibility. We also needed an easier way to handle monitoring of certain jobs and tasks, which, before, we had custom implementations to handle output logging.
- Live view of log
- Filtering and custom views
- Historical information
- Better json search support
- Regex support
- Message grouping
- Improved visibility
- Improved communication
- Decreased time to review issues
NR logging just didn't seem to work all that well for us. We had issues with logs getting to them. SolarWinds Papertrail was much simpler to set up.
Do you think SolarWinds Papertrail delivers good value for the price?
Yes
Are you happy with SolarWinds Papertrail's feature set?
Yes
Did SolarWinds Papertrail live up to sales and marketing promises?
Yes
Did implementation of SolarWinds Papertrail go as expected?
Yes
Would you buy SolarWinds Papertrail again?
Yes
Using SolarWinds Papertrail
5 - Our users are mostly developers who want to deploy code quickly and be able to test and see how things are going across the entire deployed system. To this end, we favor adding logging for new components that allow us to quickly and easily find and examine the new processes. This makes debugging easier and reduces the amount of time we have to spend to let users know that things are actually working.
1 - It's just one person. Supporting Papertrail requires minimal effort.
- debugging
- visibility of deployed systems
- real-time feedback
- telemetry
- monitoring dry-run processes in production
- radical visibility across the cluster