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
SolarWinds Kiwi Syslog Server
Score 7.5 out of 10
N/A
Solarwinds® Kiwi Syslog® Server is a syslog management tool for network and systems engineers. It receives syslog messages and SNMP traps from network devices (routers, switches, firewalls, etc.), and Linux®/Unix® hosts. Users can filter and view these messages based on time, hostname, severity, etc., and set up custom alerts. Kiwi Syslog Server has built-in actions to react appropriately to syslog messages. There are also log archival and clean-up features to help comply with security policies.
$319
Per Instance
Pricing
SolarWinds Loggly
SolarWinds Kiwi Syslog Server
Editions & Modules
Standard
$79
per month/billed annually
Pro
$159
per month/billed annually
Enterprise
$279
per month/billed annually
One Time Price
$319.00
Per Instance
Offerings
Pricing Offerings
SolarWinds Loggly
SolarWinds Kiwi Syslog Server
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No 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 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.
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.
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 …
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 …
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 …
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.
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
Syslog-ng don't have customer support or technical support .But its a free software and no clarity on limitations ingestion bandwidth. No gui feature and everything should be done from backend. Gui can easily help to start and stop service ,easy to configure. Unlimited …
PRTG Network Monitor does not give enough reporting and visibility as SolarWinds Kiwi Syslog Server provides. PRTG Network Monitor Syslog is just a sensor but SolarWinds Kiwi Syslog Server has separate applications which are very useful.
SolarWinds Kiwi Syslog is a bare-bones Syslog Server. It doesn't have the advanced features of Splunk and SolarWinds Log Analyzer such as alerting, log analysis, event correlation, etc. However, if you're an SMB and just need a solution to fulfill a security requirement, then …
PRTG is a great package and very useful, but the jump from the free 100 sensor price model to the first tier of the paid model is WAY too expensive. SolarWinds Kiwi Syslog Server is very inexpensive and provides us with the results we needed for log monitoring.
Our group already had a license for the Orion Syslog server that comes bundled with Orion NPM, but it didn't quite meet our requirements for performance. Elasticsearch and Graylog easily met our performance requirements, but not enough team members were able to manage the …
I've not had any other interaction with other Syslog servers. The main reason for that is that Kiwi works outstandingly well at what it does. Simply put, I believe this product is a staple in the IT industry and will remain as such as long as they keep the tool current and …
The price for Kiwi was acceptable and it checked off all the boxes of a product that we needed. I also considered Graylog but Kiwi was much easier to configure.
SolarWinds Loggly is great for capturing and organizing logs from 3rd party sources such as NGINX. Without SolarWinds Loggly it's really difficult to manage the logs overtime, find traffic patterns, and identify issues before they become a problem. Anyone who is routinely searching through massive log files could quickly benefit from the SolarWinds Loggly and it's capabilities.
The SolarWinds Kiwi Syslog Server does what it's supposed to do. It's a bare-bones Syslog Server. If your company is just trying to fulfill security requirements or doesn't need all the advanced features of a product such as Splunk, then Kiwi will work well and not break the bank. Using the tool is very straightforward as there aren't a lot of options outside of just viewing logs.
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
Collection of SNMP traps a reliable and stable collection server for these is crucial to troubleshooting and time to ROS. Kiwi excels at this.
Easy to install set up and train users on.
The free version is a good free tool and handy to use for personal labs and other smalle use cases.
SNMP traps to user readable format is great, sometimes syslog and smnp messages can be hard to interpret and read with out a knowledge of how to do this.
Once the logging limit is exceeded, there are no logs period. Unexpectedly noisy logs often correlate with services misbehaving and potentially leading to disruption. An outage is an awful time to lose visibility into the entire system of apps. Some ways to bridge this gap would be appreciated.
Filtering by tags is not intuitive in the web interface. You may believe that you are performing the same search and filter as last time since the tags entered are the same, however, this is often not the case. The reliable way to know that you have the same filter is to bookmark the URL. This lack of ease in usability results in devs using Loggly less than they could and implementing logs less effectively during development time (since they don't consider themselves likely to view them anyway).
Would like to see a way to onboard our less experienced devs to using Loggly effectively.
Loggly's easy setup, very good customer support, and intuitive interface make Loggly very easy to use. User access management is also very easy as we can tailor the experience for each of our developers to access the information they need without having to wade through other information. While there was a slight learning curve in how to view the logs the way some specifically wanted, everything was possible and quite easy to do.
Kiwi Syslog has the best usability of any syslog server. While not being able to offer the most features, the ones it does have are intuitive and easy to work with. Everything that it has is where you think it should be. If you can't find it in the menus, it doesn't exist.
The support team have been great when we have logged tickets or had issues, most of the time it is down to user training, however we have had a couple of bugs that they have been able to iron out for us.
Because the solution is so simple to use and implement, support wasn't very necessary. The one time I did call them to better understand where logs were stored, they were very helpful and friendly. Kiwi has been around for some time and not a lot has changed over the years, so support for it is pretty straightforward and quick.
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.
Syslog-ng don't have customer support or technical support .But its a free software and no clarity on limitations ingestion bandwidth. No gui feature and everything should be done from backend. Gui can easily help to start and stop service ,easy to configure. Unlimited technical and customer support . Even when server got shutdown will get on-call or immediate support that will helps a lot to resolve errors
Loggly has alerted us to several bugs, ranging from major to small to "would have been a major problem under load."
It's great having our disparate logs collected and the alerts we have set up around them let us know recently that somebody used an incorrect document to generate a mass email. Users were trying to log in with the link provided but getting 401s and I have an alert configured to tell me about high numbers of 4xx errors.
Metrics and alerts around metrics have given us peace of mind that automated fulfillment systems aren't going off the rails and costing us hundreds of dollars.