microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Questions about Logging
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
This article and related API reference explain about a custom logger (Microsoft.Graph.Communications.Common.Telemetry.GraphLogger class).
Q1. Why does this class exist? Am I correct that application code should log here because SDK library code logs here and both logs should be in a single location?
Q2. What is the downside if my application which uses Graph SDK library logs to custom location and does not use GraphLogger?
Q3. Where does this log physically exist? I understand that we may read the log programmatically by subscribing with observer, but I wonder if it is as easy as using EventLog Viewer for development purpose?
Q4. What is the best practice to collect this log and store in Azure Monitor or similar, so that production service operators can view for diagnostic purpose?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the linked Logging article and the Microsoft.Graph.Communications.Common.Telemetry.GraphLogger API reference. Investigate the purpose, physical destination, observer access, and Azure Monitor collection options, then document clear answers and recommended production practice for each question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- documentation, observability
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100