FTRS-4045 Implement Performance scripts for dos-ingest & ETL-ODS#1034
Merged
ManithaSrinivasa merged 5 commits intomainfrom Mar 27, 2026
Merged
FTRS-4045 Implement Performance scripts for dos-ingest & ETL-ODS#1034ManithaSrinivasa merged 5 commits intomainfrom
ManithaSrinivasa merged 5 commits intomainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds performance testing tooling under tests/performance/ to support dos-ingest CRUD load tests and ETL-ODS pipeline load/observability workflows.
Changes:
- Introduces a new JMeter test plan for dos-ingest CRUD Organisation GET/PUT testing (
DS_Test_Plan.jmx) and updates parameter loading to support per-service APIM workspaces. - Adds ETL-ODS performance scripts for (a) extracting real organisation IDs from DynamoDB, (b) injecting synthetic FHIR Organisation messages into the transform SQS queue, and (c) fetching/exporting CloudWatch metrics.
- Extends the performance
Makefileand READMEs with new targets and usage guidance.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| tests/performance/scripts/etl_ods/generate_synthetic_sqs_messages.py | Generates synthetic FHIR Organisation envelopes and sends them to the ETL-ODS transform SQS queue. |
| tests/performance/scripts/etl_ods/extract_organisation_ids.sh | Extracts Organisation IDs/ODS codes from DynamoDB into a CSV used by JMeter and injection scripts. |
| tests/performance/scripts/etl_ods/cloudwatch_metrics.py | Fetches ETL-ODS CloudWatch metrics and optionally exports CSV/JSON reports. |
| tests/performance/scripts/etl_ods/cloudwatch_config.py | Centralises ETL-ODS resource naming conventions from ENVIRONMENT/WORKSPACE. |
| tests/performance/scripts/etl_ods/README.md | Documents ETL-ODS load injection and metrics workflows. |
| tests/performance/scripts/LoadParams.groovy | Makes APIM workspace derivation configurable via a service_name JMeter property. |
| tests/performance/README.MD | Documents DS_Test_Plan usage and links to ETL-ODS tooling. |
| tests/performance/Makefile | Adds make targets for DS CRUD tests and ETL-ODS injection/metrics/extractor invocation. |
| tests/performance/DS_Test_Plan.jmx | New JMeter plan for dos-ingest CRUD performance testing (backend + proxy + stress modes). |
AITR1
reviewed
Mar 17, 2026
AITR1
reviewed
Mar 17, 2026
AITR1
reviewed
Mar 17, 2026
…S stress test docs
tamaragoldschmidt
approved these changes
Mar 26, 2026
AITR1
approved these changes
Mar 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…mance Makefile targets
Description
Context
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.