[Do not merge] Load testing Notifications

[Harriethw]

Description

Process for load testing:

FUN FACT: the dev environment and preprod share MESH inbox, so if you send stuff to mesh and it isn't acknowledged by preprod then dev will pick it up and process.

Ensure you are monitoring everything:

• Check out relevant environment on the Portal, e.g. the dashboard for links to logs and CPU - dash-manbrs-dev-notifications in the container app resource group
• One useful specific log query is checking when a job started and finished:

ContainerAppConsoleLogs_CL
| where ContainerGroupName_s startswith 'manbrs-smm'
| project TimeGenerated, ContainerName_s, Log_s
| where Log_s has "completed" or Log_s has "started"

• And log into the AVD to allow access to Blog Storage as an easy way to check/debug what's been ingested

Run the command locally:

• check out this branch
• set the NUMBER_OF_ROWS or NUMBER_OF_FILES to setup (default 5 of each - was timing out about 200 files with 200 rows each)
• In your terminal

az login

make dev notifications-load-test

• observe logs etc as described above
• Tidy up afterwards by opening a console on the web container app
  and running the delete_all_load_test_data to delete the files created.
• And delete files created in Blob Storage via the Portal UI. stmanbrs{env}

Next steps

• Do the above for preprod environment
• Document here https://nhsd-confluence.digital.nhs.uk/spaces/DTS/pages/1257635896/Load+testing+WIP

Jira link

Review notes

Review checklist

• Check database queries are correctly scoped to current_provider

[github-actions]

The review app is available at this URL:
https://pr-821.manage-breast-screening.non-live.screening.nhs.uk
You must authenticate with HTTP basic authentication. Ask the team for credentials.