Implement Server side volume monitoring
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 641
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 57
Description
Server side volume monitoring: Relating back to the drastic spikes in data volume due to a noisy implementation of a data point we have found that such spikes could be avoided with early volume detection monitoring on prereleases of product builds. In order to help prevent these data spikes, we are asking teams to implement their own volume monitoring on pre-release implementations of their products.
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 files, tests, or entry points are identified. Start by reviewing the linked Monitoring-Kusto data guidance and the repository's server-side architecture, then clarify the monitoring scope and success criteria for detecting volume spikes in prerelease builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100