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 🙌
Welcome to Signal #03!
It's that time of the month when we update our community to what we've been up to recently. This month, we left behind a trail of squashed bugs, tiny but mighty product improvements, and onboarded new contributors for our journey ahead.
We are also working on a big update on metrics ingestion for SigNoz that will massively increase the scope of performance monitoring using SigNoz. More details inside 👇
This month, we are excited to announce that our latest release had contributions from 10 awesome contributors. Release link: v0.3.3
Some of our users wanted to see 4xx errors quickly. So we have enabled regex pattern matching in our trace filters. Now users can apply generic regex operations to any of their tags.
Flamegraphs and Gantt charts make a champion combo for debugging latency issues on our dashboard. We improved the experience slightly, where selecting a trace in the flamegraph highlights the corresponding span in the Gantt chart view.
We recently conducted a deep dive into our stargazers and found out that the top 5 countries where our stargazers belong are from US, India, Brazil, China, and Germany.
To make our GitHub repo more accessible, we raised requests for getting our readme.md translated to different languages. Tony Qu, a 15+ year .NET veteran, helped translate our Readme to Chinese, and we couldn't be happier. 🤓
As we mentioned earlier, users requested to visualize 4xx as errors and be highlighted in the SigNoz dashboard. Currently, we have solved it by enabling regex operations on tags. However, we would love to have your inputs on how to visualize it better. Any UI/UX suggestion is welcomed on the issue.
With metrics ingestion pipeline, users should be able to send and visualize metrics like Dosckerstats, JMX metrics from target Mbeans server, cluster-level metrics from the Kubernetes API server, and visualize these on SigNoz UI.
This update will increase the scope of application performance monitoring manifolds. We will come out with specific tutorials on how to monitor these metrics once we launch the update.
You can find the complete list of receivers for which metrics ingestion pipeline will work here.
We recently had our monthly community call. Community calls can be joined by anyone who wants to participate.
The agenda was to discuss the best practices we should follow in our frontend code, specifically around test frameworks to use, styling guides for PRs, and localization.
Some frameworks that are used in large scale companies like Uber and Verizon were suggested for our frontend development workflow:
- RTL for component testing and integration testing
You can watch the complete call recordings here 👇
If you want to join future community calls, then you can join our slack channel. We give out all updates there.
Monitoring your Spring Boot application with OpenTelemetry was never this easy. OpenTelemetry provides a Java JAR agent that can be attached to any Java 8+ application. The JAR agent can detect a number of popular libraries and frameworks and instrument it right out of the box. You don't need to add any code for that.
You can read the full blog here👇
Thank you for taking out the time to read this issue :) If you have any feedback or want any changes with the format, please create an issue.