Distributed tracing is becoming a critical component of any application's performance monitoring stack. Setting it up in-house is a hearculean task, and that's why many companies prefer outside tools. Jaeger and Zipkin are two popular open-source projects used for end-to-end distributed tracing. Let us explore their key differences in this article.

Jaeger is an open-source end-to-end distributed tracing tool for microservices architecture. On the other hand, Elastic APM is an application performance monitoring system that is built on top of the ELK Stack (Elasticsearch, Logstash, Kibana, Beats). In this article, let's explore their key features, differences, and alternatives. Application performance monitoring is the process of keeping your app's health in check. APM tools enable you to be proactive about meeting the demands of your customers.

Jaeger and New Relic are tools used in the application monitoring and observability domain. While Jaeger is an open source tool under Cloud Native Computing Foundation, New Relic is a SaaS vendor in the observability domain. Let us explore the key differences between Jaeger and New Relic in this article. New Relic is an extensive SaaS tool and provides application performance as well as infrastructure monitoring. Jaeger provides an open-source solution for end-to-end distributed tracing.

Jaeger and OpenTracing are both open-source projects. Jaeger was originally built by teams at Uber and then open-sourced. The OpenTracing project was also started by teams at Uber, and hence they are compatible with each other. While Jaeger is an end-to-end distributed tracing tool, OpenTracing is a set of APIs and libraries that can be used to instrument your application.

Folks! Great to have you over for our monthly product update aka Signal #04. This month we made great strides in both our frontend and backend pods. Metrics ingestion, testing frameworks, improved tracking features for gRPC calls and much more! We also crossed 200+ members on our slack community 🎉🎉🎉 Let's dive in to see what humans at SigNoz have been upto!

Setting up observability and robust monitoring for distributed systems is a challenging task. Engineering teams need access to different pieces of information to understand what's happening with their application. Is OpenTelemetry a step in the right direction for distributed tracing? Let's find out. Nothing can guarantee how your systems will behave in production. Things will go wrong, and it's critical to monitor your application for any signs that need troubleshooting.

It's time for monthly product updates aka Signal #03. This month's release hit a major milestones with PRs from 10+ contributors. Let's see what humans of SigNoz have been upto 🙌

In a little over 4 months, we have crossed 4k+ stars on our GitHub repo. In this article, we explore what we can learn from our GitHub stars.

It's time for community updates #2. We're delighted to announce that SigNoz is now live with ClickHouse support. And yeah, we trended on GitHub at No.1 🎉

In this article, we dig deeper into why we decided to extend support for ClickHouse as a storage backend for SigNoz and the efficiency gains we achieved using it.