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.

Sign up for GitHub

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

Jump to bottom

Plans to bring back Dev Diagnostics? #3987

Open
k0mraid3 opened this issue Nov 21, 2024 · 0 comments
Open

Plans to bring back Dev Diagnostics? #3987

k0mraid3 opened this issue Nov 21, 2024 · 0 comments
Labels
Area-DD Related to Dev Diagnostics🔍 Issue-Feature New feature or request Needs-Triage New issue that the core contributors need to triage

Comments

@k0mraid3
Copy link

Suggested new feature or improvement

I guess this would kinda be a feat request. Are there plans to bring back Dev Diag or maybe have it as a standalone?

PS - Why did it get removed? Bug?

Scenario

I found it super useful personally and was hoping to see more feats would be added to it. Loved the "Unified" logging concept.

Additional details

N/A
@k0mraid3 k0mraid3 added the Issue-Feature New feature or request label Nov 21, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage New issue that the core contributors need to triage label Nov 21, 2024
@krschau krschau added the Area-DD Related to Dev Diagnostics🔍 label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-DD Related to Dev Diagnostics🔍 Issue-Feature New feature or request Needs-Triage New issue that the core contributors need to triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@krschau @k0mraid3