You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace Tabs with OsAwareTabs for terminal commands using named slots (#123)
* Initial plan
* Replace all Tabs with syncKey="terminal" with OsAwareTabs component
Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
* Update OsAwareTabs to use named slots and reduce code duplication
Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
* refactor: replace Fragment with div in OsAwareTabs usage for improved readability
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
Co-authored-by: David Pine <david.pine@microsoft.com>
The dashboard is configured when it starts up. Configuration includes frontend and OpenTelemetry Protocol (OTLP) addresses, the resource service endpoint, authentication, telemetry limits, and more.
@@ -18,8 +19,8 @@ There are many ways to provide configuration:
18
19
19
20
Consider the following example, which shows how to configure the dashboard when started from a Docker container:
The Aspire dashboard can be configured to receive telemetry sent from browser apps. This feature is useful for monitoring client-side performance and user interactions. Browser telemetry requires additional dashboard configuration and that the [JavaScript OTEL SDK](https://opentelemetry.io/docs/languages/js/getting-started/browser/) is added to the browser apps.
10
11
@@ -86,8 +87,8 @@ The preceding launch settings JSON file configures all profiles to include the `
86
87
87
88
If the dashboard is used standalone, without the rest of Aspire, the OTLP HTTP endpoint is enabled by default on port `18890`. However, the port must be mapped when the dashboard container is started:
88
89
89
-
<TabssyncKey="terminal">
90
-
<TabItemlabel="Bash"icon="seti:shell">
90
+
<OsAwareTabssyncKey="terminal">
91
+
<divslot="unix">
91
92
92
93
```bash
93
94
docker run --rm -it -d \
@@ -98,8 +99,8 @@ docker run --rm -it -d \
98
99
mcr.microsoft.com/dotnet/aspire-dashboard:latest
99
100
```
100
101
101
-
</TabItem>
102
-
<TabItemlabel="PowerShell"icon="seti:powershell">
102
+
</div>
103
+
<divslot="windows">
103
104
104
105
```powershell
105
106
docker run --rm -it -d `
@@ -110,8 +111,8 @@ docker run --rm -it -d `
110
111
mcr.microsoft.com/dotnet/aspire-dashboard:latest
111
112
```
112
113
113
-
</TabItem>
114
-
</Tabs>
114
+
</div>
115
+
</OsAwareTabs>
115
116
116
117
The preceding command runs the dashboard container and maps gRPC OTLP to port `4317` and HTTP OTLP to port `4318`.
117
118
@@ -123,8 +124,8 @@ If the dashboard and your app are started by the AppHost, no CORS configuration
123
124
124
125
If the dashboard is used standlone then CORS must be configured manually. The domain used to view the browser app must be configured as an allowed origin by specifing the `DASHBOARD__OTLP__CORS__ALLOWEDORIGINS` environment variable when the dashboard container is started.
125
126
126
-
<TabssyncKey="terminal">
127
-
<TabItemlabel="Bash"icon="seti:shell">
127
+
<OsAwareTabssyncKey="terminal">
128
+
<divslot="unix">
128
129
129
130
```bash
130
131
docker run --rm -it -d \
@@ -136,8 +137,8 @@ docker run --rm -it -d \
136
137
mcr.microsoft.com/dotnet/aspire-dashboard:latest
137
138
```
138
139
139
-
</TabItem>
140
-
<TabItemlabel="PowerShell"icon="seti:powershell">
140
+
</div>
141
+
<divslot="windows">
141
142
142
143
```powershell
143
144
docker run --rm -it -d `
@@ -149,8 +150,8 @@ docker run --rm -it -d `
149
150
mcr.microsoft.com/dotnet/aspire-dashboard:latest
150
151
```
151
152
152
-
</TabItem>
153
-
</Tabs>
153
+
</div>
154
+
</OsAwareTabs>
154
155
155
156
The preceding command runs the dashboard container and configures `https://localhost:8080` as an allowed origin. That means a browser app that is accessed using `https://localhost:8080` has permission to send the dashboard telemetry.
@@ -441,22 +442,22 @@ When using `Microsoft.Extensions.AI` (`IChatClient` and related abstractions), y
441
442
442
443
Many OpenTelemetry libraries support the `OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT` environment variable to enable message content capture. Set this environment variable to `true`:
The Aspire dashboard collects diagnostic data to help developers monitor and analyze their applications. Separately, when the dashboard is launched through Visual Studio or Visual Studio Code as part of a running Aspire application, Microsoft collects usage data about the dashboard itself. This data helps the Aspire team improve the product. Additionally, unhandled exception details from the dashboard are sent to Microsoft to assist in identifying and resolving issues.
9
9
@@ -20,22 +20,22 @@ Starting with Aspire 9.3, dashboard usage telemetry is enabled by default. Dashb
20
20
21
21
To opt-out of telemetry collection, set the `ASPIRE_DASHBOARD_TELEMETRY_OPTOUT` environment variable to `true`. This will apply to all users accessing the Aspire dashboard:
22
22
23
-
<TabssyncKey="terminal">
24
-
<TabItemlabel="Bash"icon="seti:shell">
23
+
<OsAwareTabssyncKey="terminal">
24
+
<divslot="unix">
25
25
26
26
```bash
27
27
export ASPIRE_DASHBOARD_TELEMETRY_OPTOUT=true
28
28
```
29
29
30
-
</TabItem>
31
-
<TabItemlabel="PowerShell"icon="seti:powershell">
30
+
</div>
31
+
<divslot="windows">
32
32
33
33
```powershell
34
34
$env:ASPIRE_DASHBOARD_TELEMETRY_OPTOUT= "true"
35
35
```
36
36
37
-
</TabItem>
38
-
</Tabs>
37
+
</div>
38
+
</OsAwareTabs>
39
39
40
40
Alternatively, you can opt-out of telemetry collection by disabling telemetry collection in the host IDE. Learn how to opt out in Visual Studio or Visual Studio Code.
@@ -33,24 +33,24 @@ For more information about using the dashboard during Aspire development, see [E
33
33
34
34
The Aspire dashboard is also shipped as a Docker image and can be used standalone, without the rest of Aspire. The standalone dashboard provides a great UI for viewing telemetry and can be used by any application.
0 commit comments