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.
$79
per month/billed annually
Pricing
SolarWinds Loggly
Editions & Modules
Standard
$79
per month/billed annually
Pro
$159
per month/billed annually
Enterprise
$279
per month/billed annually
Offerings
Pricing Offerings
SolarWinds Loggly
Free Trial
Yes
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Yes
Entry-level Setup Fee
No setup fee
Additional Details
Free trial for Standard and Pro plans for 14 days with all features.
Security Onion was a much better fit for our uses at this time. The more we integrate into a hybrid environment the more need for Loggly but at this time Security Onion accomplishes our goals.
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.
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.
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 …
SolarWinds Loggly integrates well with other SOlarWinds products, and that is ultimately why we chose to use Loggly. LogDNA was fine for our needs, but costly for only providing logging.
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 …
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 …
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 …
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 …
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 …
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 …
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 …
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 …
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 …
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