Tracing

Pinpoint Application Failures with Distributed Tracing

When building modern software architectures there can be many moving parts that while adding to the flexibility of software, can also make them more complex than ever before. With software now being built in smaller, more discrete components, issues can occur at many different layers across the stack, making them more difficult to track down.

Metrics and Logs Are Out, Distributed Tracing Is In

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.

Metrics and Logs Are Out, Distributed Tracing Is In With Chinmay Gaikwad | Kongcast Episode 5

In this Kongcast Episode, Chinmay Gaikwad, tech evangelist at Epsagon, explains why metrics and logs aren’t sufficient for companies with a microservices architecture. Instead, Chinmay recommends leveraging distributed tracing for optimal observability.

The Benefits of Bringing Together Debugging and Tracing Data

The rise in digital transformation over the past few years means that more and more companies are adopting cloud native technologies. While these distributed architectures provide scalability and agility, they also increase complexity. As Arnal Dayaratna, research director in software development for IDC, writes, “One of the challenges faced by contemporary developers is the task of understanding applications that they may not have even developed or used .”

Getting By With A Little Help From My Visual Tracing

When working with Rookout customers, one of the most commonly heard requests we hear is a plea for “context”. When trying to debug a complex applications, setting a Non-Breaking Breakpoint and fetching a full view of local variables and stack trace is a necessary first step. But in a complex, distributed environment, this first step is not always enough.

Error logging, tracing, and improving developer workflow with Jeffrey T. Fritz

Today Nico joined Jeffrey T. Fritz on the Fritz and Friends live coding stream and we talked about how Rollbar can be added to your applications to provide better logging, error tracking, and reporting. We walked through the story of Rollbar and added the logging solution to the KlipTok service that manages interactions with internet bots for the various social networks and search engines. See why 100,000+ developers trust Rollbar to analyze, diagnose & fix errors in record time.

Take your mobile monitoring to the next level

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.

Tracing With Zipkin in Kong 2.1.0

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.