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

Introduce a performance test scenario with combined datasources #35290

Open
odubajDT opened this issue Sep 19, 2024 · 3 comments
Open

Introduce a performance test scenario with combined datasources #35290

odubajDT opened this issue Sep 19, 2024 · 3 comments
Labels
enhancement New feature or request testbed

Comments

@odubajDT
Copy link
Contributor

Component(s)

testbed

Is your feature request related to a problem? Please describe.

Currently, collector does not have a performance test combining multiple datasources (traces+metrics+logs) in order to monitor the CPU and memory requirements of such scenario. In the current state of the testbed, there is no load generator providing the possibility to execute such scenario.

Since the collector is mostly used not only for isolated data types (logs/metrics/traces), but for combining all of the data types, it would be based much more on real-world usages to have a combined scenario for all data types

Describe the solution you'd like

Implement a load generator that is able to send metrics+traces+logs to be able to create a performance test combining ll 3 data sources.

Describe alternatives you've considered

No response

Additional context

Implementation of the additional combined scenario can help the community to determine the minimal requirements for running the collector in a non-isolated real-world environment as well to track the resource consumption of the collector

@odubajDT odubajDT added enhancement New feature or request needs triage New item requiring triage labels Sep 19, 2024
Copy link
Contributor

Pinging code owners:

  • testbed: @open-telemetry/collector-approvers

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

  • testbed: @open-telemetry/collector-approvers

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@atoulme
Copy link
Contributor

atoulme commented Dec 7, 2024

Could you run 3 different telemetrygen instances all pointed at the collector to perform the load with different signals? That ought to do the job, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request testbed
Projects
None yet
Development

No branches or pull requests

2 participants