Support OpenTelemetry to show logs as Structured in Aspire Dashboard
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- csharp
- Domain
- observability-sre
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the emulator's ILogger setup and its Aspire Dashboard integration, then verify that emulator logs are exported through OpenTelemetry and appear as structured logs with the dashboard's filtering and tracing-related features.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Currently all app config emulator logs show as only console in Aspire dashboard, I'd like to suggest to add support for OpenTelemetry to show the logs as Structured in Aspire Dashboard.
Describe the solution you'd like
A clear and concise description of what you want to happen.
For emulator code, do logging with ILogger, and also add dependency on open telemetry package, so that it will output to open telemetry exporter.
// Setup logging to be exported via OpenTelemetry
builder.Logging.AddOpenTelemetry();
builder.Services.AddOpenTelemetry();
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Alternative is to look at the logs in Console from Aspire dashboard, but that would miss the support for traces, and fine gained filter, as well as other feature of open telemetry.
Additional context
Add any other context or screenshots about the feature request here.
logs show up in console
logs missing from Structured.
- Dominant language
- C#
- Stars
- 38
- Forks
- 8
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/AppConfiguration-Emulator
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Azure/AppConfiguration-Emulator#95 · 3 comments · 3 reactions ·
-
Collaboration with TestContainers community for a module to support the AppConfiguration emulatorOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/AppConfiguration-Emulator#71 · 3 comments · 1 reaction ·
-
Development status of Feature Flags, Snapshots, and Real-time pushMay be free again @zhiyuanliang-ms claimed this 331 days ago, and no pull request is open. Open
Azure/AppConfiguration-Emulator#59 · 7 comments · 1 assignee ·
-
Support dark theme for AAC emulator UXMay be free again @zhiyuanliang-ms claimed this 333 days ago, and no pull request is open. Open
Azure/AppConfiguration-Emulator#57 · 1 comment · 2 reactions · 2 assignees ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Azure/AppConfiguration-Emulator#48 · 1 comment ·
All issues in Azure/AppConfiguration-Emulator
Similar issues
-
copilot documentation
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
[Rust][Flaky Test] multiple_deadlines_fire_in_order asserts a wall-clock gap instead of firing orderOpenCI/CD ⚒️ Flaky-tests 🐦
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
valkey-io/valkey-glide#7255 ·
Maintainers usually reply within 3 days
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
unoplatform/Uno.Core#99 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
aws/aws-dotnet-ai#75 ·