Welcome to Signal #02!
Quite a lot has happened since our last community updates. We had 2 major releases, crossed 4k GitHub stars and got featured in multiple newsletters. We were also trending at No.1 position on Github across all programming languages 🚀
Here we are again, to update you with what we have been upto since our last newsletter issue.
What we shipped
In our last issue, we had mentioned community demands to extend support for ClickHouse as a storage backend. And we're delighted to announce that it is now integrated with SigNoz.
When you install SigNoz, you will have an option to either go with ClickHouse or Kafka + Druid as your storage backend.
We have also written a blog with comparison between the two set ups and how ClickHouse sits in our technical architecture.
We have improved our dashboard loading time and reduced the bundle size to less than 1 mb. Our dashboards are meant to take quick actions on your issues, so we will keep on improving our frontend performance.
Gantt charts for better trace/span visualization
We have made it easier to drill down on issues causing latency in your services. With Gantt charts you can visualise your services and events in a parent-child relationship tree which makes it easier to figure out which events are causing a latency in a request call.
Some of our community members were interested in having SigNoz support eBPF based instrumentation to have faster trials. We wanted to check with the community how relevant is this for you - or are folks more comfortable with OpenTelemetry based instrumentation which we currently support? Also, since eBPF support is only available for kernel 4.14+ - we wanted to understand how many people would be able to run eBPF.
If you have any views on the above, would love it if you can add a comment to the issue.
We have been actively working on supporting 'custom metrics' to SigNoz. Once this feature is shipped, you should be able to send metrics from sources like StatsD, Prometheus, OpenTelemetry, etc. and visualise it in SigNoz dashboard.
A few things that will be enabled post metrics ingestion pipeline:
- Infrastructure metrics (CPU, memory, disk space) including K8s metrics and container metrics
- DB metrics for mysql, redis, mongo, cassandra, etc and monitoring other components like nginx, kafka, etc
- Custom metrics - you can send any metric you want to track
We conducted a workshop on Observability 101 using OpenTelemetry & SigNoz during Bengaluru's first ever Kubernetes Community Days. Ankit Nayan, our CTO talked about the importance of observability in modern-day distributed systems. We also gave a hands-on demo of SigNoz where we instrumented a Python app to set it up for monitoring with SigNoz.
Trending on GitHub 🔥
On 27th June, we found out we were trending at #1 position on GitHub worldwide across all programming languages. More than 100 million repositories are live on GitHub, and to find SigNoz right at #1 out of all these repos was an humbling experience for the team. We're extremely thankful to the entire Dev community for showing us such love 💙
On that front, we're also delighted to announce that we have crossed 4k stargazers on GitHub.⭐ We are thankful to each of you stargazers 🤓
Slack Community 👋
Our slack community is now 100+ members strong! 🎉💪 We are always looking for ways in which we can be more helpful to our community. So if you have some ideas, feel free to pitch in! You can join our slack community here. 🙌
We got featured in Golang weekly for our blog on instrumenting Golang app with SigNoz. We also got featured in DevOpsLinks by Faun.dev, one of Medium's largest DevOps publications. With these features, we are grateful to reach new developers across the globe.
From our blog
This week we want to share this article explaining how you can instrument a sample Golang application and start monitoring it with SigNoz.
SigNoz supports OpenTelemetry as the primary way for users to instrument their application. OpenTelemetry is a single, vendor-agnostic instrumentation library with support for both automatic and manual instrumentation.
Read more about how you can instrument and start monitoring Golang apps here:
How to set up Golang application performance monitoring with SigNoz
Thank you for taking out the time to read our second issue :) If you have any feedback or want any changes with the format, create an issue here.