Dear readers, We are happy to announce that Plumbr has been acquired by Splunk. Our whole team is super excited to join the Splunk product team and continue developing APM solutions on a much bigger scale. Throughout the 9 years of history, we stayed true to our goal of helping our customers with more reliable and faster digital services: Plumbr started as a memory leak detection tool (hence the... Source ..read more

Every once in a while, we get asked about how well Plumbr supports/integrates with the up-and-coming open source distributed tracing agents. Our answer has always been “Yes, that integration will be possible one day, when the agents and their data communication protocols are mature enough”. Then, that “one day” arrived… About a month ago, one of our customers pointed out to us how they... Source ..read more

The TLDR version of today’s blog post: we are expanding the number of latency metrics that Plumbr browser agent collects to include the Web Vitals. They are not yet publicly accessible in Plumbr UI though. Let us know if you’re interested in using these metrics to help us work out the best way to offer them in the Plumbr UI and API. Now, as the science of “. Source ..read more

One of the best ways to get value out of Plumbr is to define thresholds on the performance metrics that are important to you and let Plumbr alert you when these thresholds are not met. This way, you don’t need to spend time looking at the Plumbr dashboard, and can be sure that you are notified when things are not as good with user experience as they should. A crucial part of creating any... Source ..read more

Most complex applications are nowadays composed of smaller functional pieces (often called micro services) that communicate to each other over HTTP. When you develop and maintain one such service that depends on other services, your code’s performance in production does not only depend on the efficiency of your own algorithms, but also on the performance of the downstream services that your code... Source ..read more

The modern understanding of how to do observability right stands on the “three pillars of observability” – metrics, logs, and distributed traces. In order to really benefit from these three pillars, you need to implement a holistic solution that ties data from all three together. Plumbr gives metrics and distributed traces out of the box – just attach our monitoring agents and enjoy metrics... Source ..read more

Today, we are happy to announce an update that completes the automated root cause analysis feature within the Plumbr Java Agent. From now on, Plumbr can automatically explain every bottleneck in your Java code that makes your application or API slow. This means that we can relieve software engineers of enormous amounts of overhead created by the need to troubleshoot and reproduce issues and... Source ..read more

Plumbr uses tracing to provide actionable insight into your application’s performance. The traces begin in the end users’ browsers (or at the API endpoint for APIs) and cover all servers in the backend that participate in serving the user interactions (or API calls). Today, we’re happy to announce that Plumbr back-end agents can now also trace backend calls serviced by Python applications. Source ..read more

This post is following up our in-depth review of the distributed tracing concept. In this post we will look into how distributed tracing can help you respond to incidents. Let us start with a hypothetical support ticket landing on your desk: Eager to help out the customer, you dive into troubleshooting. Fast forward two weeks and you will find yourself receiving the seventh email in the series... Source ..read more

Whenever you release a new version of your application/API, you can let Plumbr know about it. As a result, Plumbr will be able to show you how availability and performance metrics change across different versions of your application. You will explicitly get answers to the following questions: Is the application really slower after the last release, as my customers claim? By how much? Source ..read more