stackabletech / stackabletech/issues
Define performance test metrics to gather
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
To make the planned performance test actually mean something we will want to gather as many metrics as we can while running the tests.
These metrics should be stored permanently and be attributable to specific test runs and scenarios to ensure we can make sense of them later on.
This includes but is not limited to:
- We want to gather jmx metrics from the products (hdfs, kafka, ...)
- NodeExporter metrics
- Network metrics
This ticket is done when:
- We have a clearly defined set of metrics that we want to collect
- Gathering these metrics has been tested at least once to ensure there are no major roadblocks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the planned performance-test setup and identifying how JMX metrics from products such as HDFS and Kafka, NodeExporter metrics, and network metrics can be collected and persisted. Define attribution to test runs and scenarios, then test the gathering process once; done means the metric set is documented and no major collection roadblocks remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka
- Domain
- observability, performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100