Skip to content

Commit 20fc782

Browse files
Merge pull request #287060 from jcjiang/patch-5
Update aspire-dashboard.md
2 parents a2381ec + ddc76ce commit 20fc782

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

articles/container-apps/aspire-dashboard.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,12 +13,24 @@ zone_pivot_groups: azure-azd-cli-portal
1313

1414
# Read real time app data with .NET Aspire Dashboard in Azure Container Apps (preview)
1515

16-
The [.NET Aspire Dashboard](/dotnet/aspire/fundamentals/dashboard/overview) provides information on how your app is running both on the environment and individual app level, which can help you detect anomalies in real time and debug errors. The dashboard shows data for all Container Apps that is part of your project, regardless of language or runtime.
16+
The [.NET Aspire Dashboard](/dotnet/aspire/fundamentals/dashboard/overview) displays live data about how applications and other resources are running within an environment.
1717

1818
The following image is a screenshot of a trace visualization generated by the .NET Aspire Dashboard.
1919

2020
:::image type="content" source="media/aspire-dashboard/aspire-dashboard-trace.png" alt-text="Screenshot of a .NET Aspire Dashboard trace window.":::
2121

22+
The information displayed on the dashboard comes from two sources:
23+
24+
- 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.
25+
26+
- **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.
27+
- **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.
28+
- **Logs** record all events and errors that take place during the running of the application. This information is useful for finding when a problem occurred and correlated events.
29+
30+
- The Kubernetes API provides information about the underlying Kubernetes pods on which your application is running on and their logs.
31+
32+
The dashboard is secured against unauthorized access and modification. To use the dashboard, a user must have 'Write' permissions or higher - in other words, they must be a Contributor or Owner on the environment.
33+
2234
## Enable the dashboard
2335

2436
::: zone pivot="portal"

0 commit comments

Comments
 (0)