Item: SolarWinds Loggly
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

We have a lot of integrations between different websites and API's that run in the background. This is sometimes hard to monitor. We use SolarWinds Loggly to keep progress and error logs, fetch statistics on the amount of errors, and get notifications when errors occur. This improved our ability to monitor these integrations immensely.

Pros and Cons

Keeping logs from different integrations in 1 place
Being able to filter to find the relevant logs
Sending notifications when some logs occur

More options when setting up alerts would be welcome
Being able to update an alert query once it is created
When selecting 'view before and after events', keep the same search parameters (tags, for example)

Return on Investment

We can solve problems quicker, often before the customer notices
We get more useless alerts, because the alert logic isn't extensive enough
Everyone now uses the same log format

Key Insights

Do you think SolarWinds Loggly delivers good value for the price?

Yes

Are you happy with SolarWinds Loggly's feature set?

Yes

Did SolarWinds Loggly live up to sales and marketing promises?

Yes

Did implementation of SolarWinds Loggly go as expected?

Yes

Would you buy SolarWinds Loggly again?

Yes

Likelihood to Recommend

SolarWinds Loggly is well suited for keeping track of your code to find the source of an error. If you structure your logs well, you can filter out all unnecessary logs and only keep the ones you need, so you can find the problem more quickly. It is less suited for detailed alert logic.

I'm very happy with SolarWinds Loggly!

Overall Satisfaction with SolarWinds Loggly