Complex modern systems are the new reality for infrastructure teams, and this is due to the evolution of Cloud Computing and working with Distributed systems, containerization, and microservices by default. The teams now have different infrastructures and virtual services with which they must take care of scalable, reliable, and performative applications.
In Node.js, you can centralize tracing information generated by V8, Js code, and userspace code. Directly in the APMs, tracing means that you will have a detail of each flow in your application's process; this means that you will have records available of each time a function is called or a database or external information is called. With tracing, you will have a way to capture, visualize and analyze traces across complex architectures, including architectures that use monoliths and microservices.
In this episode of Kongcast, I spoke with Chinmay Gaikwad, the tech evangelist at Epsagon, about distributed tracing and observability for microservices architectures. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.
Colin Hemmings, Senior Product Manager of Bitrise Trace shares his experience in mobile monitoring and its challenges in this behind-the-scenes interview.
While there’s room for debate in what constitutes sufficient monitoring for a mobile app, it’s no question that if you wait long enough for users to report issues, then soon you will have no users. For most mobile development teams, you are not measured against how many features you deliver or bugs you fix, but by how successful your app is and how much value it delivers to users. As a result, you need to know where the app is providing a subpar experience and why.
Trace is our new mobile monitoring add-on that has been in public beta since late February. It is also available to you if you have a Bitrise account, so if you want to dive into it, here's where you should start.
There is a great number of logging plugins for Kong, which might be enough for your needs. However, they have certain limitations: Most of them only work on HTTP/HTTPS traffic. They make sense in an API gateway scenario, with a single Kong cluster proxying traffic between consumers and services. Each log line will generally correspond to a request which is “independent” from the rest.
