Skip to main content
TrustRadius
SolarWinds Loggly

SolarWinds Loggly

Overview

What is SolarWinds Loggly?

Loggly is a cloud-based log management service provider. It does not require the use of proprietary software agents to collect log data. The service uses open source technologies, including ElasticSearch, Apache Lucene 4 and Apache Kafka.

Read more
Recent Reviews

TrustRadius Insights

Loggly has proven to be an invaluable tool for a wide range of use cases, allowing users to effectively troubleshoot and prevent issues. …
Continue reading

Loggly rocks

8 out of 10
December 15, 2020
Incentivized
Loggly is a neat a straight forward product. We use to centralize most of our application and security logs, including WAF data which we …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing

Standard

$79

Cloud
per month/billed annually

Pro

$159

Cloud
per month/billed annually

Enterprise

$279

Cloud
per month/billed annually

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://www.loggly.com/plans-and-pricing

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Details

What is SolarWinds Loggly?

Unified Log Analysis and Log Monitoring

With environments spanning on-premises, hybrid, and public cloud environments, IT operations and application teams are inundated with unrelated events, issues, and logs. Every outage or slowdown directly impacts the business, either in lost productivity or lost revenue. Issues must be diagnosed rapidly and resolved across all the dynamically changing components underpinning your heterogeneous web applications, services, and infrastructure.

SolarWinds® Loggly® is presented by the vendor as a cost-effective, hosted, and scalable full-stack, multi-source log management solution combining powerful search and analytics with comprehensive alerting, dashboarding, and reporting to proactively identify problems and significantly reduce Mean Time to Repair (MTTR).

SolarWinds Loggly Features

  • Supported: Highly responsive search at scale
  • Supported: Interactive shareable dashboards
  • Supported: Anomaly detection and alerts
  • Supported: Dynamic Field Explorer™
  • Supported: Rapidly pinpoint bottlenecks and failure points
  • Supported: Collaborate with all stakeholders
  • Supported: New shared agent that collects metrics and logs
  • Supported: Add trace context to your logs

SolarWinds Loggly Screenshots

Screenshot of Streamlined Log AnalysisScreenshot of Monitoring & AlertingScreenshot of Screenshot of Screenshot of

SolarWinds Loggly Integrations

SolarWinds Loggly Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Supported CountriesAll
Supported LanguagesEnglish, Spanish

Frequently Asked Questions

Loggly is a cloud-based log management service provider. It does not require the use of proprietary software agents to collect log data. The service uses open source technologies, including ElasticSearch, Apache Lucene 4 and Apache Kafka.

Splunk Enterprise, Sumo Logic, and Rapid7 InsightOps are common alternatives for SolarWinds Loggly.

Reviewers rate Usability highest, with a score of 7.8.

The most common users of SolarWinds Loggly are from Mid-sized Companies (51-1,000 employees).

SolarWinds Loggly Customer Size Distribution

Consumers0%
Small Businesses (1-50 employees)25%
Mid-Size Companies (51-500 employees)50%
Enterprises (more than 500 employees)25%
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(79)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Loggly has proven to be an invaluable tool for a wide range of use cases, allowing users to effectively troubleshoot and prevent issues. With its syslog digest capabilities, users can sift through logs to identify the root cause of outages and errors, creating alerts for future prevention. By serving as an aggregation point for streaming logs from network access switches and core routers, Loggly efficiently manages large volumes of data. This makes it a valuable tool for support and engineering teams, providing alerting, monitoring, and issue triage solutions. Additionally, Loggly acts as a central repository for logs from PHP-based apps and servers, offering reports, analysis, and aggregation from different sources. Its flexibility extends to monitoring and debugging large-scale application platforms leveraging multiple microservices. By providing detailed information across different environments, Loggly enables efficient issue tracking and resolution. It also aids in meeting auditing requirements by logging network activity and providing proof of network monitoring. Furthermore, Loggly is widely used to troubleshoot systems, gain insights into performance and health, and visualize trends through its dashboard and alarm capabilities. Whether it's monitoring web traffic, capturing logs to identify security threats on internal and external websites, or monitoring integrations between websites and APIs, Loggly proves to be an essential tool in enhancing monitoring capabilities. Its ability to capture the behavior of software applications during development allows for easier investigation and setting up alerts to prevent service disruptions. Loggly is considered a modern platform for log-file analysis due to its compatibility with Linux systems, plaintext config files, utilization of web standards, and open-source friendly nature. Overall, Loggly plays a crucial role in troubleshooting server and application issues by providing effective solutions for resolving problems.

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.

Confusing User Interface: Many users have expressed frustration with Loggly's user interface, stating that it is confusing and difficult to navigate. They find it challenging to perform tasks effectively due to this issue, which negatively impacts their overall experience with the platform.

Cumbersome Query Language: Some users have found Loggly's query language to be cumbersome and unintuitive. They believe that using the query language adds unnecessary complexity to their log analysis process, making it more time-consuming and challenging to extract meaningful insights from their logs.

Difficulty in Sending Logs: Several users have encountered difficulties when trying to send logs to Loggly, particularly depending on the source system they are using and the level of control they have over it. This has caused inconvenience for these users as they face challenges in seamlessly integrating their logs into Loggly for effective analysis and monitoring.

Users commonly recommend considering alternatives and exploring other options in addition to Loggly. They suggest looking into different logging and monitoring solutions before making a decision.

Another common recommendation is to ensure the correct data is inputted and to tweak the data sending process if necessary. Users advise being careful with the data that is being sent to Loggly and making any necessary adjustments to improve the accuracy of the logs.

Integrations and tools are also mentioned as important factors to consider. Users suggest looking into the available integrations and using tools to build the desired structure for log management and analysis.

It is worth noting that some users recommend spending time reducing log noise and standardizing the log entry process. They emphasize the importance of streamlining the logs to avoid unnecessary clutter and confusion.

Additionally, users suggest using Fluentd as an adapter to ensure Loggly receives all the necessary information. They find it helpful for ensuring smooth communication between systems.

Having someone knowledgeable who can provide training on Loggly is also recommended by users. They believe that having assistance from an expert can greatly enhance the user experience.

Organizing requests and their results is another recommendation made by users. They find Loggly useful in this regard, as it helps them keep track of their requests and easily access the corresponding results.

While many users find Loggly to be a good initial solution, some mention that costs can increase as usage grows. It is advised to keep this in mind when considering long-term usage of the platform.

Overall, users describe Loggly as an excellent solution for debug log management and analysis. They appreciate its functionality, especially with the addition of the live-tail client. Some users compare Loggly to LogEntries and note that they find Loggly to have better polish.

Attribute Ratings

Reviews

(1-25 of 38)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We found that Loggly is a very good balance between functionality and costs. With the ability to analyze different log files across different platforms gives it just a bit of a bigger edge compared to other monitoring systems.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Loggly was the easiest to use and the one that really allowed us to get a full view of what's going on with our services, and proactively solve problems.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
With Loggly we can manage not only AWS apps but all the apps we have (not only Cloud-based apps).
It is also very convenient to add users that need to have access to a given log streams: we do not need to manage an AWS IAM role/user.
And the search engine is way more easy and very human-friendly!
Sean Patterson | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
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.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Loggly proved to be very easy to set up and integrate with our existing systems without having to add extra agents or roll our own everything. Insights others give for Java performance may be better than we've seen with Loggly, but in terms of log aggregation and data insights based on them, it's the best value.
October 02, 2020

Fire and forget logs

Score 8 out of 10
Vetted Review
Verified User
Incentivized
I actually couldn't get anybody from Datadog to engage with me, the main problem we had was that our devices couldn't connect to an encrypted port, but we didn't want to send our logs in plain text over the internet. We implemented an on-net log aggregator which then connects to Loggly over encrypted UDP. In theory Loggly made this particularly easy providing configuration snippets for most of the common log services (e.g. rSyslog, syslog-ng). Unfortunately the documentation was out of date and none of the provided configs worked, fortunately they were close enough that combined with our own syslog-ng experience we were able to get it up and going relatively painlessly. The choice then of going with Loggly, backed by an industry favourite in Solarwinds was a no brainer.
Simon Clarke | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We have a Nagios Log Server, however needed specialist help to get it running before it fell over, which is why we went down the Loggly route.
We also use Microsoft Cloud App Security, however we find using this as well as Loggly gives us double the power to search for issues and resolve them.
Score 2 out of 10
Vetted Review
Verified User
Incentivized
Loggly was a mistake. We selected it to get a cheap vendor-hosted solution up and running quickly but have come to regret the decision and should have spent the effort to set up the right tool from the beginning.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Graylog would also have met our requirements, but since we then needed to run a virtual machine (with huge disk space) and also needed more work for setup and maintenance, our calculations resulted in Loggly being more cost effective.
Icinga is not made for log file monitoring and only used to monitor server health like CPU, memory, disk space ...
September 30, 2020

Log it real, with Loggly

Score 8 out of 10
Vetted Review
Verified User
Incentivized
Loggly is at another level at indexing and search experience. However, since CloudWatch has the full history with least cost it is always the fallback. So if Loggly has something like S3 glacier kind of feature for keeping old logs which are least accessed with less cost, that would nice.
Score 4 out of 10
Vetted Review
Verified User
Incentivized
I've used ELK, Sumo, Splunk, Cloudtrail/watch, Sentinel. You get what you pay for. If you have the time, expertise, and budget for a Splunk setup, you can't beat it. ELK is great for OSS shops but takes more hand-holding to scale and stabilize. Loggly, for us, was closer to the easy/cheap side of the spectrum, but as we didn't explore the paid options we can't really compare the power features.
September 29, 2020

Loggly is good

Score 9 out of 10
Vetted Review
Verified User
Incentivized
I honestly didn't shop around that much. I came from CloudWatch, which though it has been improving, was very frustrating when it came to just setting up a simple alarm when a specific log message is found, or extracting useful metrics from logs. Loggly was recommended to me by a business partner and the timing worked out when SolarWinds reached out to me and offered me a discount (we were extremely price sensitive at that time, like this rest of the world at the beginning of the pandemic).
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Price and ease of deployment were huge factors in our decision to use Loggly. Loggly is actually within reach for most companies while also being very easy to setup. Elasticsearch, for instance, had wildly outdated documentation when I was previewing all these tools so I was unable to get it working at all; but the worst part was their support refused to provide any pre-sales setup information. Graylog enterprise pricing was ludicrously expensive. Sumo Logic was ok but still priced much higher. We expected Azure Monitor to be decent but it was just pure garbage for the price; the setup was convoluted and Azure as a whole feels like a perpetual beta.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
I have used EFK stack (ElasticSearch, Fluentd, and Kibana) and Splunk. Solarwind Loggly is the most flexible managed service out of these solutions and suitable for companies embracing the SaaS model
Return to navigation