dotnet / dotnet/docs

No documentation on how to use an external scope provider when logging

Open
#40,763 0 comments 2 reactions 0 assignees View on GitHub
:watch: Not Triaged dotnet-fundamentals/svc
Dominant language
No language data
Stars
4.8k
Forks
6.1k
Avg merge
15h 21m
Merged PRs (30d)
370

Description

### Type of issue

Missing information

### Description

I can see by looking at the source code that there is support to use an external scope provider:

- IExternalScopeProvider
- ISupportExternalScope

As a side note, the following is not helpful (comment taken from within the IExternalScopeProvider source code itself)...
"Represents a storage of common scope data."

There are no docs on what this mysterious feature is or how to use it. Some people have managed to decipher it enough to use it as there are issues in github relating to not being able to pass in a scope provider to some log providers, but a quick google reveals not much is said on the topic.

This is what ChatGPT has to say on it:

> Implement the IExternalScopeProvider Interface: Create a class that implements the IExternalScopeProvider interface. This interface includes methods for pushing and popping scopes and for setting the scope provider for the logging framework.

What a developer would mainly be interested in here is what is the reason for using an external scope provider over the out-of-the-box functionality and how would they go about doing so?

### Page URL

https://learn.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=command-line

### Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/extensions/logging.md

### Document Version Independent Id

0e787ac2-1108-1d94-d62f-ccffa93e06c3

### Article author

@IEvangelist

### Metadata

* ID: 346bbcf3-9f8e-b253-09fe-906195392783
* Service: **dotnet-fundamentals**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.