requested changes

Makefile

@@ -16,6 +16,7 @@ TESTNET_RPC ?= https://testnet-validated-validator-rpc.poktroll.com/ # TestNet R
 APPGATE_SERVER ?= http://localhost:42069
 GATEWAY_URL ?= http://localhost:42079
 POCKET_ADDR_PREFIX = pokt
+LOAD_TEST_CUSTOM_MANIFEST ?= loadtest_manifest_example.yaml
 
 # The domain ending in ".town" is staging, ".city" is production
 GROVE_GATEWAY_STAGING_ETH_MAINNET = https://eth-mainnet.rpc.grove.town
@@ -403,11 +404,11 @@ test_e2e_settlement: test_e2e_env ## Run only the E2E suite that exercises the s
 test_e2e_params: test_e2e_env ## Run only the E2E suite that exercises parameter updates for all modules
 	go test -v ./e2e/tests/... -tags=e2e,test --features-path=update_params.feature
 
-.PHONY: test_load_relays_stress_example
-test_load_relays_stress_example: ## Run the stress test for E2E relays on a persistent (non-ephemeral) remote (devnet) chain. Note that this is just an example.
+.PHONY: test_load_relays_stress_custom
+test_load_relays_stress_custom: ## Run the stress test for E2E relays using custom manifest. "loadtest_manifest_example.yaml" manifest is used by default. Set `LOAD_TEST_CUSTOM_MANIFEST` environment variable to use the different manifest.
 	go test -v -count=1 ./load-testing/tests/... \
 	-tags=load,test -run LoadRelays --log-level=debug --timeout=30m \
-	--manifest ./load-testing/loadtest_manifest_example.yaml
+	--manifest ./load-testing/$(LOAD_TEST_CUSTOM_MANIFEST)
 
 .PHONY: test_load_relays_stress_localnet
 test_load_relays_stress_localnet: test_e2e_env warn_message_local_stress_test ## Run the stress test for E2E relays on LocalNet.

docusaurus/docs/operate/infrastructure/devnet.md

@@ -122,7 +122,7 @@ image:
   tag: sha-7042be3
 ```
 
-As all parameters in this config are passed to the [downstream helm chart](https://github.com/pokt-network/protocol-infra/tree/main/charts/full-network) via an [ArgoCD Application](https://github.com/pokt-network/protocol-infra/blob/main/clusters/protocol-us-central1/devnets-persistent.yaml).
+All parameters in this config are passed to the [downstream helm chart](https://github.com/pokt-network/protocol-infra/tree/main/charts/full-network) via an [ArgoCD Application](https://github.com/pokt-network/protocol-infra/blob/main/clusters/protocol-us-central1/devnets-persistent.yaml).
 Here is a [list of all options](https://github.com/pokt-network/protocol-infra/blob/main/charts/full-network/values.yaml) which can be modified, in addition to the image tag.
 
 ### Scaling actors up and down
@@ -176,8 +176,8 @@ IMAGE_TAG=sha-7042be3 NAMESPACE=devnet-sophon JOB_NAME=e2e-test-7042be3 POCKET_N
 
 ### Staking actors
 
-Since the genesis actor keys are the same as LocalNet, we can use the same commands (and keyring) to stake actors on DevNet. Additionally, DevNets
-match the hostnames with LocalNet, which makes it possible for the same stake configs to work on different networks.
+Since the genesis actor keys are the same as LocalNet, we can use the same commands (and keyring) to stake actors on
+DevNet. Additionally, DevNets match the hostnames with LocalNet, making it possible for the same stake configs to work on different networks.
 For example, this command stakes supplier2 on DevNet `devnet-sophon`:
 
 ```bash

docusaurus/docs/operate/testing/load_testing.md

@@ -71,7 +71,10 @@ To execute tests on LocalNet:
 #### Interpreting Results
 
 - The CLI output displays standard Go test results. Successful tests are indicated by `PASS`, while failures are denoted by `FAIL` with accompanying error messages.
-- During test execution, the observability stack continuously collects metric data from off-chain actors. On LocalNet, [Grafana is accessible on port 3003](http://localhost:3003/?orgId=1). The "Stress test" and "Load Testing" dashboards provide valuable insights into system status.
+- During test execution, the observability stack continuously collects metric data from off-chain actors. On LocalNet, [Grafana is accessible on port 3003](http://localhost:3003/?orgId=1). The
+  [Stress test](http://localhost:3003/d/ddkakqetrti4gb/protocol-stress-test?orgId=1&refresh=5s)
+  and [Load Testing](http://localhost:3003/d/fdjwb9u9t9ts0e/protocol-load-testing?orgId=1) dashboards provide valuable
+  insights into system status.
 
 ### Non-Ephemeral Networks (TestNets, MainNet, etc)
 
@@ -93,10 +96,18 @@ Using [loadtest_manifest_example.yaml](https://github.com/pokt-network/poktroll/
 
 #### Test Execution
 
-Utilize the provided makefile target to run the `relays_stress.feature` with the modified manifest:
+Utilize the provided makefile target to run the `relays_stress.feature` with the modified manifest. By default, the example manifest file is used. You can specify a different manifest file by setting the `LOAD_TEST_CUSTOM_MANIFEST` environment variable.
+
+To run the stress test using the default manifest:
+
+```bash
+make test_load_relays_stress_custom
+```
+
+To run the stress test with a custom manifest:
 
 ```bash
-make test_load_relays_stress_example
+LOAD_TEST_CUSTOM_MANIFEST=your_new_manifest.yaml make test_load_relays_stress_custom
 ```
 
 #### Result Analysis