opensearch-project / opensearch-project/data-prepper
Automate Performance Testing
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
As a user that wants to run performance tests on my pipeline configuration, setting up performance testing is a tedious manual process.
As a developer that wants to test the performance of a new plugin that I have created, setting up and running the performance tests is a tedious manual process.
Describe the solution you'd like
- Automate the deployment of the performance testing environment (data prepper installation, gatling, prometheus, grafana) so that anyone can deploy a separate instance of this environment with a couple simple commands (this means multiple users could run their performance tests independently and in parallel)
- After the environment is deployed, make it easy to run the performance test suites with different Data Prepper configurations. Ideally, this should be as simple as editing the configuration, and the clicking "Run Tests".
- Running performance tests should only cost resources when tests are actually being run (just deploying the environment doesn't cost money, and after a test is being run no billing is done)
Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
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
No files, tests, or entry points are named. Start by mapping how Data Prepper performance tests and their deployment are currently run, including the proposed Gatling, Prometheus, and Grafana environment. Done should cover repeatable environment deployment, configurable test runs, independent parallel instances, and no resource cost outside test execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, java, prometheus
- Domain
- devops, observability, performance, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100