PowerShell / PowerShell/vscode-powershell
PSES Additional Telemetry for Preformance Metrics
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- I have written a descriptive issue title.
- I have searched all issues to ensure it has not already been reported.
Summary
In order to help improve the stability of the extention, having telemetry events for when PSES LSP is down would be helpful to know. An enumerated list of items that would be useful to know about PSES:
- How often is PSES down?
- How often does it crash?
- How long does it take to conenct from extension to language server?
Adding telemetry events to answer these questions would give us a better understanding of the reliability of PSES and customers experience with it.
Proposed Design
No response
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
The issue names no files, tests, or entry points. Start by identifying the PSES LSP lifecycle and existing telemetry in the TypeScript VS Code extension; done means telemetry can measure downtime, crashes, and extension-to-language-server connection time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- developer-experience, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100