microsoft / microsoft/ApplicationInsights-JS
[Supportability] Consider feature to enable console tracing using Cookie
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 685
- Forks
- 261
- Avg merge
- 21h 33m
- Merged PRs (30d)
- 5
Description
In some cases it is hard to understand what is going on with Application Insights SDK. Console tracing may help troubleshoot the issue. But change of console trace level require re-instrumentation.
I suggest to create an alternative way to change tracing level for Application Insights SDK using cookies or other runtime setting.
Contributor guide
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
No file, test, or entry point is named in the issue, so begin by locating the Application Insights SDK's console tracing configuration and runtime initialization path. Define how a cookie or other runtime setting selects the tracing level, then verify that the level can change without re-instrumentation and that the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, javascript, typescript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100