Help Center/ Well-Architected Framework/ Well-Architected Framework and Practices/ Operational Excellence Pillar/ OPS06 Observability System/ OPS06-05 Implementing Dependency Telemetry

Updated on 2025-05-22 GMT+08:00

View PDF

OPS06-05 Implementing Dependency Telemetry

Risk level
High
Key strategies
Dependency telemetry monitors the running status and performance of components and external services that workloads depend on. It collects high-value metrics on accessibility, timeout, and other key events related to dependencies such as DNS, databases, or third-party APIs. When you monitor an application to publish dependency-related metrics, logs, and traces, you can better understand potential bottlenecks, performance issues, or failures that could impact workloads.

Parent topic: OPS06 Observability System

Previous topic: OPS06-04 Standardizing Application Logs

Next topic: OPS06-06 Performing Distributed Tracing

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.