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.

Excited to launch our first newsletter. We are delighted to have crossed 1.6k stars on GitHub, growing more than 30% last month. Catch up on what we're upto at SigNoz!

Not all industries are the same in terms of the sensitivity of data they handle. And as you mature as a company, you need to be more careful of how you handle your critical data. With the advent of modern cloud native technologies & Kubernetes, on-prem software is more viable now.

Why we felt there was a need for a full stack open source observability platform and how we went about building it.

In this post we want to lay out typical price which someone would incur in running SigNoz. This would give potential users an idea of what resources they would need to provision & typical monthly cost at different application load and sampling rates.