If you're looking for an open-source alternative to AppDynamics, then you're at the right place. SigNoz is a perfect open-source alternative to AppDynamics. SigNoz provides a unified UI for both metrics and traces with advanced tagging and filtering capabilities. In today's digital economy, more and more companies are shifting to cloud-native and microservice architecture to support global scale and distributed teams.

Modern digital organizations have rapidly adopted microservices-based architecture for their applications. Microservices-based apps have components designed around business capabilities serving a specific purpose. It enables smaller engineering teams to own specific services that lead to increased productivity. But componentization also leads to complexity. Today’s modern internet-scale businesses have hundreds or thousands of microservices.

There are standalone distributed tracing tools like Jaeger, and there are APM tools that do not provide distributed tracing capabilities. In this article, we will see how distributed tracing complements an APM tool for a holistic performance monitoring experience. Both APM and distributed tracing are critical tools to understand the performance of your applications. And if your application is facing performance issues impacting customer experience, you need to understand what’s causing it fast.

GraphQL is a query language for APIs developed by Facebook in 2012. It was then open-sourced in 2015. GraphQL enables frontend developers or consumers of APIs to request the exact data that they need, with no over-fetching or under-fetching. In this article, we will learn how to monitor GraphQL APIs with the open-source APM tool, SigNoz. GraphQL has become a popular alternative to REST because of its ease of use. It enables developers to pull data from multiple data sources in a single API call.

Microservices architecture allows technology companies to build application services around business capabilities. It enables rapid development and also boosts developer productivity. But it also introduces complexity. Troubleshooting and operating an internet-scale application based on microservices is hard. And that’s where distributed tracing comes into the picture. Traditional monolithic application architecture is easy to develop, deploy and monitor.

One who moves the hill sets off by taking away the rocks. This is our 10th monthly update, and looking back at it, I can’t help feeling proud of our consistent efforts. Numerous releases, GitHub issues, sprints, and standups have brought us here. And it’s incredible to see what small teams with purpose can build with a consistent effort. Without further ado, let’s see what our 10th edition has to offer.