open-telemetry/opentelemetry-dotnet

Metrics stress test improvements

Open

#2,373 opened on Sep 17, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (889 forks)auto 404
help wantedinfrakeep-openmetrics

Repository metrics

Stars
 (3,725 stars)
PR merge metrics
 (PR metrics pending)

Description

Similar to this, https://github.com/open-telemetry/opentelemetry-dotnet/issues/2372, we need to improve the Stress test to cover more scenarios.

  1. Add more scenarios similar to above.
  2. Make the stress run run indefinitely (until cancelled eg: by a key press).
  3. Modify stress test to include validation as well - i.e have parallel Collects() and validate that the expected values are collected. (similar to https://github.com/open-telemetry/opentelemetry-dotnet/pull/1086)

Contributor guide

Research direction
Inspect the existing stress tests in the repository, reference the linked issue #2372 for additional scenarios, implement indefinite run with cancellation, and add parallel validation for collected metrics.
Tech stack
csharp
Domain
backendtesting
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50