Update articles/container-apps/aspire-dashboard.md

Co-authored-by: Jason Wells <[email protected]>

Author: Jiachen Jiang

articles/container-apps/aspire-dashboard.md

@@ -21,7 +21,7 @@ The following image is a screenshot of a trace visualization generated by the .N
 
 The information displayed on the dashboard comes from two sources:
 
-- OpenTelemetry (OTel), an open-source library for tracking **traces**, **metrics**, and **logs** for your applications. [This documentation](https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/telemetry) provides more information on how the Aspire dashboard integrates with OTel.
+- OpenTelemetry (OTel), an open-source library for tracking **traces**, **metrics**, and **logs** for your applications. [This documentation](/dotnet/aspire/fundamentals/telemetry) provides more information on how the Aspire dashboard integrates with OTel.
 
     - **Traces** track the lifecycle of requests - how a request is received and processed as it moves between different parts of the application. This information is useful for identifying bottlenecks and other issues.
     - **Metrics** are real-time measurements of the general health and performance of the infrastructure - for example, how many CPU resources are consumed and how many transactions that the application handles per second. This information is useful for understanding the responsiveness of your app or identifying early warning signs of performance issues.