-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
remove oteltestbed collector #34849
remove oteltestbed collector #34849
Conversation
Note that this immediately changed the memory consumed by the collector, which is surprising since i didnt change the config:
|
Thanks |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
This collector is only used by the load tests. This is confusing because it's a custom distro that isn't shipped anywhere. This PR updates the load tests to use the otelcontribcol which is at least closer to the contrib distro. We should probably move to officially shipped distros in the near future. Signed-off-by: Alex Boten <[email protected]>
Signed-off-by: Alex Boten <[email protected]>
b2eca0c
to
c3b3484
Compare
The reason a separate build is used is because the contrib build's memory footprint changes based on all components, even if they are not used in the testbed. This means that the testbed's memory thresholds are regularly invalidated and the net result is that tests become very flaky and the thresholds keep getting raised arbitrarily to deal with the problem. Original explaination. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
The generated code was removed in a separate PR and after discussing this we're not ready to remove it yet |
This collector is only used by the load tests. This is confusing because it's a custom distro that isn't shipped anywhere. This PR updates the load tests to use the otelcontribcol which is at least closer to the contrib distro. We should probably move to officially shipped distros in the near future.