Open odubajDT opened 2 months ago
Pinging code owners:
testbed: @open-telemetry/collector-approvers
See Adding Labels via Comments if you do not have permissions to add labels yourself.
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:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
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