Retrace (formerly APM+) is a lightweight Application Performance Management solution. Retrace gives developers continuous, real-time analysis through a combination of code-level visibility with in-line log and error data. Retrace helps identify top performance offenders by analyzing top page requests, top SQL queries, and top external web services.
$99
up to 3 servers, 500,000 traces, and 1,000,000 logs
Pricing
Logstash
Retrace
Editions & Modules
No answers on this topic
Essentials
$99
up to 3 servers, 500,000 traces, and 1,000,000 logs
Perfect for projects where Elasticsearch makes sense: if you decide to employ ES in a project, then you will almost inevitably use LogStash, and you should anyways. Such projects would include: 1. Data Science (reading, recording or measure web-based Analytics, Metrics) 2. Web Scraping (which was one of our earlier projects involving LogStash) 3. Syslog-ng Management: While I did point out that it can be a bit of an electric boo-ga-loo in finding an errant configuration item, it is still worth it to implement Syslog-ng management via LogStash: being able to fine-tune your log messages and then pipe them to other sources, depending on the data being read in, is incredibly powerful, and I would say is exemplar of what modern Computer Science looks like: Less Specialization in mathematics, and more specialization in storing and recording data (i.e. Less Engineering, and more Design).
If I need to change a logo design on the invoice, the new logo is slightly larger or smaller so the type below the logo is in a different area than before. In this case, you would need to load the new version of the document into APM Plus and redo the mapping of the field areas to properly grab the information needed to process the document. Without doing this, the document could fail or go to the wrong archive based on the fields.
Logstash design is definitely perfect for the use case of ELK. Logstash has "drivers" using which it can inject from virtually any source. This takes the headache from source to implement those "drivers" to store data to ES.
Logstash is fast, very fast. As per my observance, you don't need more than 1 or 2 servers for even big size projects.
Data in different shape, size, and formats? No worries, Logstash can handle it. It lets you write simple rules to programmatically take decisions real-time on data.
You can change your data on the fly! This is the CORE power of Logstash. The concept is similar to Kafka streams, the difference being the source and destination are application and ES respectively.
Since it's a Java product, JVM tuning must be done for handling high-load.
The persistent queue feature is nice, but I feel like most companies would want to use Kafka as a general storage location for persistent messages for all consumers to use. Using some pipeline of "Kafka input -> filter plugins -> Kafka output" seems like a good solution for data enrichment without needing to maintain a custom Kafka consumer to accomplish a similar feature.
I would like to see more documentation around creating a distributed Logstash cluster because I imagine for high ingestion use cases, that would be necessary.
To set up the fields that APM Plus monitors, you need to map each field area on each document.
APM Plus could use a way to link the documents back into the finance or business software so you can find the document under the PO, Sales Order, Invoice, etc.
APM Plus setup is only for the professionals. There are many areas that need tweaking on setup, having a better default setup would lessen the learning curve to set it up for use.
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
It is a very impressive tool which doesn't overwhelm you with unnecessary data. They have combination of tools that haven't seen by any other company which makes it a very powerful tool
Positive: Learning curve was relatively easy for our team. We were up and running within a sprint.
Positive: Managing Logstash has generally been easy. We configure it, and usually, don't have to worry about misbehavior.
Negative: Updating/Rehydrating Logstash servers have been little challenging. We sometimes even loose data while Logstash is down. It requires more in-depth research and experiments to figure the fine-grained details.
Negative: This is now one more application/skill/server to manage. Like any other servers, it requires proper grooming or else you will get in trouble. This is also a single point of failure which can have the ability to make other servers useless if it is not running.
APM Plus has freed up users from having to manually attach documents to each place they are sending it. APM Plus will do it automatically.
APM Plus provides a searchable archive to re-visit sent documents with customers and vendors. Having to reprint a document you risk the potential that something has changed since it was last printed.
APM Plus does need IT staff for adjustments and to review sending problems. Not for an average user.
