diff --git a/deployment/terraform/create.go b/deployment/terraform/create.go
index 2130f0d78..b231d32d7 100644
--- a/deployment/terraform/create.go
+++ b/deployment/terraform/create.go
@@ -561,6 +561,10 @@ func (t *Terraform) updateAppConfig(siteURL string, sshc *ssh.Client, jobServerE
 	// Setting to * is more of a quick fix. A proper fix would be to get the DNS name of the first
 	// node or the proxy and set that.
 	cfg.ServiceSettings.AllowCorsFrom = model.NewString("*")
+	cfg.ServiceSettings.EnableOpenTracing = model.NewBool(false)    // Large overhead, better to disable
+	cfg.ServiceSettings.EnableTutorial = model.NewBool(false)       // Makes manual testing easier
+	cfg.ServiceSettings.EnableOnboardingFlow = model.NewBool(false) // Makes manual testing easier
+
 	cfg.EmailSettings.SMTPServer = model.NewString(t.output.MetricsServer.PrivateIP)
 	cfg.EmailSettings.SMTPPort = model.NewString("2500")
 
@@ -599,8 +603,10 @@ func (t *Terraform) updateAppConfig(siteURL string, sshc *ssh.Client, jobServerE
 	cfg.SqlSettings.DataSourceReplicas = readerDSN
 	cfg.SqlSettings.MaxIdleConns = model.NewInt(100)
 	cfg.SqlSettings.MaxOpenConns = model.NewInt(100)
+	cfg.SqlSettings.Trace = model.NewBool(false) // Can be enabled for specific tests, but defaulting to false to declutter logs
 
-	cfg.TeamSettings.MaxUsersPerTeam = model.NewInt(50000)
+	cfg.TeamSettings.MaxUsersPerTeam = model.NewInt(200000)      // We don't want to be capped by this limit
+	cfg.TeamSettings.MaxChannelsPerTeam = model.NewInt64(200000) // We don't want to be capped by this limit
 	cfg.TeamSettings.EnableOpenServer = model.NewBool(true)
 	cfg.TeamSettings.MaxNotificationsPerChannel = model.NewInt64(1000)
 
diff --git a/docs/faq.md b/docs/faq.md
index 9bf163357..3ebe8a28f 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -100,8 +100,32 @@ Two considerations:
 - Due to [this issue](https://github.com/grafana/grafana/issues/32585), you need to be logged in to access the Snapshot option in the Share dialog. Although logging in is not usually needed in these temporal instances, you can still do so for this purpose with the credentials `admin`/`admin`.
 - Note that a snapshot, although very useful for reference, is not a fully-functioning dashboard, so you will not be able to query new data using it. Take a look at the example above to understand how it works.
 
+### Can I stress test the ElasticSearch jobs?
+ElasticSearch schedules a daily job for aggregating posts. For configuring this, one needs to modify the Mattermost server's setting `ElasticsearchSettings.PostsAggregatorJobStartTime`, which accepts a hard-coded time (local to the machine running the server) formatted as a string like `"15:04"`.
+If you want to stress test this specific job during a load-test, you can use the [config patch](config/deployer.md#mattermost-config-patch-file) setting in the deployer config to change it to a time where the test will be running, using a partial Mattermost config like the following one:
+
+```json
+{
+    "ElasticSearchSettings": {
+        "PostsAggregatorJobStartTime": "19:34"
+    }
+}
+```
 ## Troubleshooting
 
+### Increase debugging level
+
+For troubleshooting purposes, the first step should be increasing the debugging level of both the Mattermost server and the agents:
+- For the Mattermost server, a [config patch](config/deployer.md#mattermost-config-patch-file) can be used, with a partial config that can contain the following:
+```json
+{
+    "LogSettings": {
+        "FileLevel": "DEBUG"
+    }
+}
+```
+- For the agents, the [`LogSettings.FileLevel` setting of the config.json file](config/config.md#file-level) should be set to `"DEBUG"` as well.
+
 ### Users are not connecting
 
 Make sure that both `Enable Account Creation` and `Enable Open Server` settings are set to `true` in MM System Console.