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.
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
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.
SolarWinds Loggly has many tools for analyzing application logs on different platforms. It ran Elastic Search on our behalf and eliminated the need to develop our own logging solution—errors in learning tool integration. We needed a central location for server, client app, etc. logs. We also wanted a way for our team to review data without production access. With the live-tail client, Loggly is now the best value. Although we have considered using Datadog as an alternative, it is similar/less priced to Loggly and lacks the polish of Loggly.
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.
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!
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.
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.
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.
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.
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.
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 ...
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.
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.
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).
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.
LogRhythm SIEM platform is a totally different solution but we tried using it prior to getting SolarWinds Loggly. We were able to get it to do some stuff but it wasn't as flexible (understandably). I do also like that Loggly is a hosted solution so it lowers our costs overall since we don't need to host/manage a server for this.