Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automated stability test #1022

Closed
tigrannajaryan opened this issue May 26, 2020 · 0 comments
Closed

Automated stability test #1022

tigrannajaryan opened this issue May 26, 2020 · 0 comments
Assignees
Milestone

Comments

@tigrannajaryan
Copy link
Member

We need an automated long-running stability test. The test should use the perf testbed and run for configurable period of time (e.g. 1 hour). The test should monitor the resource usage and ensure there are no performance degradations: increase of CPU usage, increase of RAM / memory leaks over time.

The test should for a short period of time of time in the default test suite. We want to have additional CircleCI job for long running tests like this, where it should run for the full duration.

@tigrannajaryan tigrannajaryan added help wanted Good issue for contributors to OpenTelemetry Service to pick up and removed feature request labels May 26, 2020
@tigrannajaryan tigrannajaryan removed the help wanted Good issue for contributors to OpenTelemetry Service to pick up label May 27, 2020
@tigrannajaryan tigrannajaryan added this to the Beta 0.4 milestone Jun 3, 2020
@dmitryax dmitryax assigned dmitryax and unassigned tigrannajaryan Jun 9, 2020
@flands flands modified the milestones: Beta 0.4, Beta 0.5 Jun 16, 2020
tigrannajaryan pushed a commit that referenced this issue Jun 17, 2020
Extracted out TestResultsSummary (in testbed/testbed/results.go), DataProvider (in testbed/testbed/data_provider.go), OtelcolRunner (in testbed/testbed/otelcol_runner.go), TestCaseValidator (in testbed/testbed/validator.go) interfaces with multiple implementations. Added tracing correctness tests in testbed/correctness using the testbed with different implementations of the 5 interfaces listed than what the perf tests use.

**Link to tracking Issue:** Provides the support to cleanly implement #652, #1022, #1023, #1027, #1031

**Testing:** All existing testbed-driven tests still pass. Correctness tests run without any panics. Correctness tests are reporting a number of bugs with translations.

**Documentation:** Godocs on all public methods.
tigrannajaryan pushed a commit to open-telemetry/opentelemetry-collector-contrib that referenced this issue Jun 22, 2020
End-2-end tests running for an hour with fixed resource limits. If limits are reached tests fail.

Current state of the collector shows a slow grow in the memory usage, which may indicate a memory leak that needs to be investigated. Once this solved, this tests can be upgraded to not use a fixed limit, but check resources consumption at the beginning and making sure it doesn't grow more than in a specified small percentage after that.

**Link to tracking Issue:** open-telemetry/opentelemetry-collector#1022
wyTrivail pushed a commit to mxiamxia/opentelemetry-collector that referenced this issue Jul 13, 2020
…telemetry#1062)

Extracted out TestResultsSummary (in testbed/testbed/results.go), DataProvider (in testbed/testbed/data_provider.go), OtelcolRunner (in testbed/testbed/otelcol_runner.go), TestCaseValidator (in testbed/testbed/validator.go) interfaces with multiple implementations. Added tracing correctness tests in testbed/correctness using the testbed with different implementations of the 5 interfaces listed than what the perf tests use.

**Link to tracking Issue:** Provides the support to cleanly implement open-telemetry#652, open-telemetry#1022, open-telemetry#1023, open-telemetry#1027, open-telemetry#1031

**Testing:** All existing testbed-driven tests still pass. Correctness tests run without any panics. Correctness tests are reporting a number of bugs with translations.

**Documentation:** Godocs on all public methods.
wyTrivail pushed a commit to mxiamxia/opentelemetry-collector-contrib that referenced this issue Jul 13, 2020
End-2-end tests running for an hour with fixed resource limits. If limits are reached tests fail.

Current state of the collector shows a slow grow in the memory usage, which may indicate a memory leak that needs to be investigated. Once this solved, this tests can be upgraded to not use a fixed limit, but check resources consumption at the beginning and making sure it doesn't grow more than in a specified small percentage after that.

**Link to tracking Issue:** open-telemetry/opentelemetry-collector#1022
hughesjj pushed a commit to hughesjj/opentelemetry-collector that referenced this issue Apr 27, 2023
…y#1022)

Bumps [boto3](https://github.com/boto/boto3) from 1.20.21 to 1.20.22.
- [Release notes](https://github.com/boto/boto3/releases)
- [Changelog](https://github.com/boto/boto3/blob/develop/CHANGELOG.rst)
- [Commits](boto/boto3@1.20.21...1.20.22)

---
updated-dependencies:
- dependency-name: boto3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Troels51 pushed a commit to Troels51/opentelemetry-collector that referenced this issue Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants