In part 3 of this 4 part series, you’ll learn how to capture critical APM data—such as hits, errors, and latency—for external service calls, allowing you to track external service SLOs.

To try this out for free for 14 days, sign up at: https://dtdg.co/tips

Distributed tracing and flame graphs allow you to easily see the performance of your application services. However, reliance on external services provides one more vector for latency and potential slowdowns. In this video we’ll show how you can instrument your code to capture external service performance and add your external services to the Datadog UI, so you can track their aggregate performance over time. By seeing latency, hit rate, and error rate coming from external services, you can define and track SLOs for those services. You can even alert on any anomalous behavior created by them—so you immediately know where to look if something goes wrong.