Azure / Azure/azure-functions-powershell-opentelemetry
Write-FunctionsOpenTelemetryLog throws ArgumentException when log/level is null
Open
- Dominant language
- C#
- Stars
- 2
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Better handling of this case -
* Default level?
* Write error to error stream instead of faulting
* Refine exception message
Contributor guide
Research direction
Start by locating the Write-FunctionsOpenTelemetryLog implementation and reproduce the ArgumentException when log/level is null. The issue lists several possible outcomes—defaulting the level, writing to the error stream, or refining the exception—so the expected behavior must be clarified before implementation; done should include handling the null case without the current failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100