Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for using .NET Aspire Dashboard (Standalone) as alternative observability stack #19

Closed
ThorstenHans opened this issue Oct 9, 2024 · 1 comment · Fixed by #21

Comments

@ThorstenHans
Copy link
Contributor

The .NET Aspire Dashboard could also act as single container observability stack. Compared to PLG and other stacks, standalone .NET Aspire Dashboard is way more lightweight.

After looking at the current implementation, I would prefer adding a single flag to spin otel setup. If the flag is present, a different compose.yaml file will be used. I would introduce a simple Stack type, to make this extensible (simplifies adding additional observability stacks in the future).

Other commands should not be affected from this change, as we will still leverage underlying docker compose.

@ThorstenHans
Copy link
Contributor Author

.NET Aspire Dashboard supports header based authentication for its OTLP(s) endpoint. However, Spin does not support this yet.

I've created a corresponding issue at fermyon/spin#2880

Although we could run .NET Aspire Dashboard without using authentication for its OTLP endpoint(s), users will be presented with a prominent warning in the dashboard UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant