Logstash vs. SolarWinds Papertrail

Logstash is a must in an ELK stack, which I am sure is going to be the #1 case. At any point when you have several sources, Logstash can be the common point to aggregate, and categorize those data. Then send this new data to its destination. Very handy. It is free and open source. It may not be appropriate to analyze data-sets dependent on each other but from a different data source. Reason being Logstash works on data at hand, and not wait for other data to arrive. It would be unwise for Logstashh to handle complicated, long-running transformations because this is injected and ejected. The faster you do it, the safer.

Incentivized

SolarWinds Papertrail is great if you have multiple separate applications and you want to be able to view and search all the logs in one place. It also works well for alerts based on certain keywords in log entries (for example, ERROR, WARN, etc.) Since only the first four weeks of logs are searchable in Papertrail, it may not work well for use-cases where much older log entries need to remain searchable.

Incentivized

• Plugin ecosystem allows modular extensions.
• Tight integration into the Elastic.com products of Beats and Elasticsearch, so minimal setup is required when using those tools.
• Filter plugins are powerful for extracting and enriching input data.

Incentivized

• Collects logs from many sources in real time.
• Makes it really easy to filter logs to dig into the logs of many services working simultaneously.
• Alerts triggered on certain search matches.

Incentivized

• Memory: Logstash is a HOG, if you are deploying it on commodity (i.e. cheap and old) hardware: You will need at least 2GB, just for Logstash. So don't expect to run your entire ELK stack on one AMD Athlon machine.
• Overlap: Logstash fills in an area of the ELK stack that makes the most sense: as a log file transformer / shipper. However, if you start breaking that stack, with the addition of other components- you start seeing where features of Logstash may be implemented or solved in the additional components much easier (or better, or to a higher degree of resolution)
• More Overlap: Since my team employs Syslog-ng extensively- Logstash can sometimes get in the way (and this may be a problem for DevOps stacks overall): You can configure Syslog to record certain information from a source, filter that data, and even export that data in a particular format. Logstash will pick that data up, and then parse it. However, if you don't keep your Syslog-ng configuration files, and your Logstash configuration files in sync, your results will not be what you expected, and this will translate into (sometimes) hours/days of work, hunting down a line item in a configuration file.

Incentivized

• The CLI was a bit clunky and required some Linux-y thought to get right (obviously more designed with scripting in mind)
• Tracking logs in real time (think something like `tail`) wasn't wildly intuitive
• Accessing/searching archives required a lot of CLI-style pulling/extracting/reg-exing

Incentivized

We are definitely going to continue using Papertrail. It's been a lifesaver.

Incentivized

As I said earlier, for a production-grade OpenStack Telco cloud, Logstash brings high value in flexibility, compliance, and troubleshooting efficiency. However, this brings a higher infra & ops cost on resources, but that is not a problem in big datacenters because there is no resource crunch in terms of servers or CPU/RAM

It's extremely easy to use. I and new colleagues have never had any issues configuring this tool or setting it up, it works almost out of the box with very simple instructions to follow to configure it to our own environment. I would highly recommend it on that ability alone.

Incentivized

I honestly have never had the need to use the support team, as we have not run into any issues so far. If we did however, judging from how the tool itself works, I don't doubt that the team would provide excellent support for any issues that we may possibly run into.

Incentivized

MongoDB and Azure SQL Database are just that: Databases, and they allow you to pipe data into a database, which means that alot of the log filtering becomes a simple exercise of querying information from a DBMS. However, LogStash was chosen for it's ease of integration into our choice of using ELK Elasticsearch is an obvious inclusion: Using Logstash with it's native DevOps stack its really rational

Incentivized

I selected SolarWinds Papertrail because it was cheap and already provided precisely the integration surface required by the Heroku stack. It probably provided the least number of 'useful' features (out of the bunch) due to the nature of my logs and the post-mortem updates that were required to make them usable.

Incentivized

• It is very difficult to give any figures on ROI, as it depends on many factors, and in a Telcocloud environment, it is much complex to find out; however, I would give some points below on ROI
• ROI based on flexibility is very high, as it reduces the time to find RCA
• ROI based on integration is very high because it supports multi-vendor environments, avoiding vendor lock-in & works across multi-cloud setups
• ROI on resource consumption is less because Logstash in 2-3 times more resource-intensive as compared to its lightweight alternatives resulting in latency

• We are alarmed properly so it makes it easy for us to monitor the server.
• Very easy to debug our apps when something's gone wrong (bug) in the production server.
• Noticed whenever any third party scan was going on our server.

Incentivized