SolarWinds Loggly Information Reviews & Insights

Score5.1 out of 10

80 Reviews and Ratings

Community insights

TrustRadius Insights for SolarWinds Loggly are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Intuitive and Easy to Use Interface: Users consistently praise Loggly's intuitive and easy-to-use interface, stating that it simplifies tasks and makes them easier to perform. The user-friendly design allows for quick navigation and access to log data, enhancing overall usability.

Highly Effective Alerting System: Many users appreciate the flexibility and effectiveness of Loggly's alerting system, finding it easy to set up alerts for specific events. Notifications can be received through email or Slack, ensuring that users stay informed about critical issues in their applications.

Comprehensive Integration Options: Reviewers value the extensive integration options provided by Loggly, which support a wide range of log sources and platforms. This feature enables users to consolidate logs from different sources into a centralized location for monitoring and analyzing data effectively.

SolarWinds Loggly Reviews

15 Reviews

InformationComputer Software7Computer Networking1Internet3Telecommunications3Information Services1

Centralized data for post mortem to detect the next calamity before it happens

Rating: 9 out of 10

Incentivized

December 2, 2022

Use Cases and Deployment Scope

We use Loggly as a syslog digest. Normally it is an after-the-fact tool for outages and anomalies. Syslog is an invaluable tool when troubleshooting outages and errors. As we experience outages we go back and sift through Loggly to see what the messages looked like at the event time and create alerts based on them to catch the problems in advance the next time. As a secondary method of catching issues before they become problems, we monitor the gross volume of messages daily. When they spike on a given day we know that something is up and go and find the offending source. Many times we catch the problem before it causes a customer impact event.

Pros

syslog digest
alerts based on syslog contents
sanity check on number of daily log events
post mortem on outages

Cons

the interface could be more intuitive
repetitive syslog dialog could either be highlighted or ignored by user choice
when a source spikes it's name could be included in the volume alert email

Likelihood to Recommend

Loggly is a great resource initially to post-mortem your errors and outages. After identifying the respective log events it can help you set alerts to keep you ahead of the game next time. When a box experiences a hard failure it can take days to recover the local syslog for troubleshooting but Loggly already has the messages. It greatly reduces time and even increases security since my team only needs Loggly access and not CLI-level authentication on all my servers. Overall, Loggly saves time, increases security, alerts me before my customers see the issues, and always provides the forensics needed to identify the root cause of an outage.

TONY HINES

Ingrastructure and Automation Manager in Information Technology at Altaworx, LLC. (Telecommunications, 11-50 employees)

Vetted Review

2 years of experience

Loggly's as easy to use as a Linux tail

Rating: 9 out of 10

Incentivized

October 5, 2020

Use Cases and Deployment Scope

As we provide a PaaS to both internal employees and our partners, SolarWinds Loggly is essential to monitoring and diagnosing our cloud-based infrastructure. It's been essential for both our development team and our IT group to monitor usage and performance while also identifying and resolving any issues that come up.

Pros

Fast setup and deployment.
Very customizable.
Searching and sorting relevant data is intuitive.

Cons

It's not free.
Won't run stand-alone on-premises.
Doesn't look as slick as some other alternatives.

Likelihood to Recommend

Loggly is primarily useful for combining logs into one centralized location. The insights that the dashboards provide also allow us to identify bottlenecks between microservices. We've had multiple instances where the ability to filter logs by keywords and seeing multiple servers' logs at the same time helped identify problems immediately. This has saved us days of troubleshooting.

Verified User

Professional in Information Technology (Telecommunications company, 11-50 employees)

Vetted Review

1 year of experience

Fire and forget logs

Rating: 8 out of 10

Incentivized

October 2, 2020

Use Cases and Deployment Scope

We use Loggly as an aggregation point to stream logs from network access switches and core routers. There can be quite a lot of data and existing solutions relied on older database technologies which broke down after a time and we'd have to manually intervene to truncate tables, etc. Loggly manages the entire process for us and just works.

Pros

Keeps working!
Fast searches.
Easy to configure searches - you don't have to be an expert in RegExp...

Cons

Not all searches are intuitive.
We have to use a log aggregating device to ship our logs to Loggly as our network devices can not connect on an encrypted protocol. I would prefer if we could use some sort of VPN-based connector to ship logs securely.
Sometimes when drilled down, it can be difficult to fully reset a search term to back all the way out of a drill down.

Likelihood to Recommend

It is well suited to very large volumes of logs where the immediate past is the area of interest, e.g. in situations where the issues are in the recent past. Loggly makes it very easy to search for particular terms of interest, within a specific time frame across the entire estate of devices or, indeed, within a subset, or on a specific device of interest. There does seem to be a short delay in the logs though, even with the "live tail" feature, Loggly might be less suited to "emerging" situations where the issues are occurring in real time.

Ciaran Kendellen

CTO (Chief Technical Officer) in Engineering at Host Ireland Business Broadband (Telecommunications, 11-50 employees)

Vetted Review

1 year of experience

Great tool, love it!

Rating: 9 out of 10

Incentivized

September 10, 2020

Use Cases and Deployment Scope

We are using Loggly to troubleshoot our systems and getting better understanding about our overall performance and health. This tool helps us visualize simply trends by using its dashboard, tracks occurrences and even as monitoring tool by leveraging its alarms capabilities. As of today Loggly is being used in many LivePerson business units however some are using different tools like Kibana for example.

Pros

Simple search.
Great visualization.
Easy to use.
Very practical.

Cons

Maybe examples of advanced filtering.

Likelihood to Recommend

Every respectable software company would log its application for tracking and monitoring. In many cases, developers tend to log too many things and eventually it's becoming a mess to understand what is going on. Loggly is helping you to find what you need easily inside all of this pile of information and that's not trivial.

I can think only about the benefits at this point:

1. Investigate production issues.

2. Visualize trend.

3. Count occurrence.

4. Exporting data.

Tomer Sofer

R&D Group Manager in Engineering at LivePerson (Computer Software, 1001-5000 employees)

Vetted Review

1 year of experience

View profile

A great cloud-based managed log aggregation and search solution.

Rating: 8 out of 10

Incentivized

September 8, 2020

Use Cases and Deployment Scope

SolarWinds Loggly is used for centralized application logging, search, and graphing. It is used by Engineering, Quality Assurance, Tech Operations, Tech Support, and Services Org to quickly search and locate application errors, metadata and event count. Loggly built-in features enable trending and performance tracking of the full application stack.

Pros

Visually represent event count via bar graphs.
Statistical function for graphing medium and 95th percentile performance metrics.
Fast return of search results.
Supports log streaming via Fluent.

Cons

The price model for the log ingestion rate is rigid and pushes for a higher usage commitment for companies with variable log generation due to weekly or monthly patterns.
Does not support long term cold storage as an option for uploaded logs.
Limited to no integration with other Solarwinds MSP product lines.

Likelihood to Recommend

Excellent performance and service reliability. Easy and intuitive web GUI. The option of multiple accounts to separate access and log aggregation between Dev/QA, staging and production environments. Easy to implement and supports multiple log streaming methods. Logs can be categorized and configured to restrict access.

Verified User

Executive in Information Technology (Computer Software company, 201-500 employees)

Vetted Review

2 years of experience

A startup engineer's review on Loggly

Rating: 9 out of 10

Incentivized

August 29, 2020

Use Cases and Deployment Scope

We used it to aggregate logs from all our servers, mostly for DevOps and debugging purposes. I didn't do the initial setup so I don't know how much effort it takes. But it sure is easy to maintain.

Pros

Quick customer supports. I found an issue and the customer service provided some workarounds before the final fix.
Easy HTTP integration. I integrated into my own Lambda function so I can process logs with my own logic.
Speedy (majority of the time).
Clean UI.

Cons

Cooler Charts/Dashboard.
More intelligent input prompts.

Likelihood to Recommend

It's an easy-to-set-up log management tool. Big enterprise might want to set up their own ELK stack because one stack, but for smaller companies, the opportunity cost is much lower to manage logs with commercial solutions like Loggly or its alternatives such as Splunk.

When I was in my previous company there were teams taking care of the ElasticSearch and Logstash so I only needed to use Kibana. In my current startup, I feel it's easier to use Loggly.

Verified User

Engineer in Engineering (Computer Software company, 1-10 employees)

Vetted Review

1 year of experience

Detailed logging without much setup.

Rating: 7 out of 10

Incentivized

May 20, 2019

Use Cases and Deployment Scope

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.

Pros

Aggregation
Filtering
Detailed Information

Cons

Configuration
Visualization
Organization

Likelihood to Recommend

Loggly is well suited to be a "catch all" for information that you don't need to have highly sorted/analyzed. It is schemaless in nature, which makes it a great fit for web logs, server logs, and other types of information. Because it is schemaless, it will not be a good for for situations where you need to aggregate and track specific log information.

Sean Patterson

Software Development Director in Information Technology at Fresh Consulting (Internet, 51-200 employees)

Vetted Review

1 year of experience

View profile

Loggly: a great Commercially-Oriented Log Shipping / Filter Pipeline, that will add value to your Company DevOps Department

Rating: 10 out of 10

Incentivized

March 27, 2019

Use Cases and Deployment Scope

While Loggly is not technically open-source, it is a modern platform for log-file analysis. Oftentimes, in our projects we will acquire competing DevOps stacks, in order to evaluate their effectiveness for us. Our criteria is usually very simple: 1. Does it work? 2.) Does it work on Linux? 3.) Does it use .config file format, or similar plaintext config files? (we generally try to stay away from XML-based file formats, or proprietary formats (think: binary), due to the overhead, and complexity that we feel does not work for us) 4.) is it modern? (i.e. if there is a UX component to the project, does it employ web-standards, such as NodeJS, HTML5, Angular, et. al) 5. It is open-source friendly? (i.e. is it built with Open Source tools, or is the Licensing less restrictive than Microsoft EULA?) Technical difficulty is almost never a concern for my team.

Pros

Modern: Loggly is modern: Dashboards, realtime information and the ability speak many different data sources and environments makes it an attractive choice
Configurability: Loggly gets log parsing right: by allowing you to in real time- filtering of log data, tagging and identifying data sources
DevOps friendly: Loggly is very Componentized: You can have an instance of Loggly running that will Monitor your Linux instance, in addition to all of it's services, as an example. Also, you can start/stop Loggly, without affecting your other components

Cons

Commodity: Loggly is protected by the company's need to convert Loggly into a retail product. While this is fine for the Company, it may limit individual developers from having immediate access to a product they would otherwise adopt. Therefore, Loggly really is geared towards Companies and Commercial Entities
Feature creep: Loggly stands in competition with other packages that are open-sourced. And while this is not bad from a Commercial view point (every needs to eat, right?), it almost automatically makes it a 2nd place package, without adding in a killer feature that adds additional value to Developers and DevOps Analysts
Parsing: Sometimes, when working with other packages, you get used to a configuration format. Loggly is not so dissimilar that it's hard to read / write, but it's not a one-to-one with say, Logstash. This is more of an annoyance than a real problem, and if you include putting your files into a Repo, then this is even less an annoyance.

Likelihood to Recommend

Loggly is a great replacement for LogStash, if your project dictates features that LogStash does not have, that Loggly does (which, I can't really think of).

The only real feature of Loggly that most (myself included) can defend, is its cloud logging. Other than that, Loggly does not offer so many more features that Logstash could not replace.

I am recommending Loggly highly, though because its learning curve is so small, that in a commercial environment, where analysts are exposed to it for the first time will have no trouble wrapping their minds around it, and thus can add it to their resume as a real skill. This is really the only real environment for modern, DevOps based software that's not open source: a commercial environment where a company can absorb the cost, and thus maintain control over their investment, also while allowing its employees the ability to easily do what open source platforms are doing for the individual DevOps Analyst/Developer.

Verified User

Engineer in Corporate (Computer Software company, 1-10 employees)

Vetted Review

7 years of experience

A very good service but a little bit pricey

Rating: 7 out of 10

Incentivized

March 22, 2019

Use Cases and Deployment Scope

We tried Loggly in some of our servers for the monitoring and alerting of log files. We used it with Nginx on Ubuntu Linux. The problem was that it was too painful to monitor logs and find the necessary information without an app because logs are huge and you must log in every day with SSH and inspect all logs

Pros

Implementation. The implementation was pretty straight forward and worked very well. Also, it has a Laravel package.
Alerting. Creating alerts with emails or Slack was a piece of cake.
Filtering. Filter your logs was very easy and fast.
UI is very simple and easy to use.

Cons

Price. If you compare it to other similar apps it is very pricey. Especially for storage and user limitations.
Amazon S3 archiving is only for the pro package. Other apps give it for free.

Likelihood to Recommend

Suitable for companies with a few users and not a lot of data. If you want something fast and light, you have 1-2 users monitoring the logs and you want a simple UI and you don't have a lot of data I believe Loggly is the best. If you have a lot of users and a lot of data then Loggly may not be for you.

Marios Vasiliou

Senior Lead Engineer in Engineering at Softline Computer Systems LTD (Information Services, 1-10 employees)

Vetted Review

1 year of experience

Easy to setup.

Rating: 6 out of 10

Incentivized

March 2, 2019

Use Cases and Deployment Scope

We wanted to do log centralization for enterprise networking product.

Pros

Capturing Django Logs
Easy to install
Capturing system logs

Cons

The main concern was that the agent that installed the software was sending data to the cloud. We didn't know what all the data was being sent.

Likelihood to Recommend

Easy to install and quick to setup. Easy setup for a Django stack.

Verified User

Engineer in Information Technology (Computer Networking company, 10,001+ employees)

Vetted Review

Loading Reviews List....

Loggly: a great Commercially-Oriented Log Shipping / Filter Pipeline, that will add value to your Company DevOps Department

Rating: 10 out of 10

Incentivized

March 27, 2019

Use Cases and Deployment Scope

Pros

Modern: Loggly is modern: Dashboards, realtime information and the ability speak many different data sources and environments makes it an attractive choice
Configurability: Loggly gets log parsing right: by allowing you to in real time- filtering of log data, tagging and identifying data sources
DevOps friendly: Loggly is very Componentized: You can have an instance of Loggly running that will Monitor your Linux instance, in addition to all of it's services, as an example. Also, you can start/stop Loggly, without affecting your other components

Cons

Commodity: Loggly is protected by the company's need to convert Loggly into a retail product. While this is fine for the Company, it may limit individual developers from having immediate access to a product they would otherwise adopt. Therefore, Loggly really is geared towards Companies and Commercial Entities
Feature creep: Loggly stands in competition with other packages that are open-sourced. And while this is not bad from a Commercial view point (every needs to eat, right?), it almost automatically makes it a 2nd place package, without adding in a killer feature that adds additional value to Developers and DevOps Analysts
Parsing: Sometimes, when working with other packages, you get used to a configuration format. Loggly is not so dissimilar that it's hard to read / write, but it's not a one-to-one with say, Logstash. This is more of an annoyance than a real problem, and if you include putting your files into a Repo, then this is even less an annoyance.

Likelihood to Recommend

Verified User

Engineer in Corporate (Computer Software company, 1-10 employees)

Vetted Review

7 years of experience