Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Logging Scope filtering #36006

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
Closed
kadukf opened this issue Jan 8, 2020 · 3 comments
Closed

Logging Scope filtering #36006

kadukf opened this issue Jan 8, 2020 · 3 comments
Labels
area-Extensions-Logging backlog-cleanup-candidate An inactive issue that has been marked for automated closure. feature-request no-recent-activity

Comments

@kadukf
Copy link

kadukf commented Jan 8, 2020

The problem we are facing with the scopes is that any code can populate the scope, e.g. ASP.NET Core code. This means any sensitive/private information can be logged in a plain text format.

Proposal: having ability to define scope treatment level, same way as loglevel.

More information here: https://fknet.wordpress.com/2020/01/08/asp-net-core-logging-scope-filtering/
@analogrelay analogrelay transferred this issue from dotnet/extensions May 7, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label May 7, 2020
@Dotnet-GitSync-Bot
Copy link
Collaborator

I couldn't figure out the best area label to add to this issue. Please help me learn by adding exactly one area label.

@analogrelay analogrelay added this to the Future milestone May 7, 2020
@maryamariyan maryamariyan removed the untriaged New issue has not been triaged by the area owner label Jul 1, 2020
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels Apr 21, 2025
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@dotnet-policy-service dotnet-policy-service bot removed this from the Future milestone May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-Extensions-Logging backlog-cleanup-candidate An inactive issue that has been marked for automated closure. feature-request no-recent-activity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@analogrelay @kadukf @maryamariyan @Dotnet-GitSync-Bot