Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/gatling/gatling.io-doc/llms.txt

Use this file to discover all available pages before exploring further.

Gatling Enterprise Edition can send automatic notifications to your team’s communication tools as soon as a simulation run ends. Each notification includes a summary of the simulation, the final run result (Successful, Assertions failure, etc.), and the individual assertion results if your simulation includes assertions. This keeps your team informed about load test outcomes without requiring anyone to log in to the platform.
Notification configuration is available to Gatling Enterprise Edition administrators only. Notifications are sent via incoming webhooks, so you must create a webhook in the target platform before configuring it in Gatling Enterprise Edition.

Supported Notification Channels

Slack

Receive simulation run results directly in any Slack channel via an incoming webhook.

Microsoft Teams

Receive simulation run results in any Microsoft Teams channel via an incoming webhook connector.

Slack Notifications

Step 1 — Create a Slack Webhook

Follow the official Slack incoming webhooks documentation to create a webhook targeting the channel where you want notifications to appear. Your webhook URL will look like:
https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
Keep this URL ready for the next step.

Step 2 — Configure in Gatling Enterprise Edition

1

Navigate to Notifications

Go to your Organization configuration page and select the Notifications tab.
2

Enable Slack Notifications

Click the toggle next to the Slack section to activate notifications.
3

Paste the Webhook URL

Enter your Slack webhook URL in the text field.
4

Test and Save

Click Test to send a hello-world verification message to your Slack channel, confirming the webhook works. Then click Save to persist the configuration.
Use the Test button before saving to verify the webhook is working and messages arrive in the correct channel.

Disabling Slack Notifications

Click the toggle in the Notifications tab to deactivate notifications and confirm your choice. Disabling notifications deletes the webhook URL from Gatling Enterprise Edition storage — it is not retained after deactivation.

Microsoft Teams Notifications

Step 1 — Create a Teams Webhook

Follow the official Microsoft Teams incoming webhooks documentation to create an incoming webhook connector targeting the target channel. Your webhook URL will look like:
https://xxxxx.webhook.office.com/xxxxxxxxx
Keep this URL ready for the next step.

Step 2 — Configure in Gatling Enterprise Edition

1

Navigate to Notifications

Go to your Organization configuration page and select the Notifications tab.
2

Enable Teams Notifications

Click the toggle next to the Microsoft Teams section to activate notifications.
3

Paste the Webhook URL

Enter your Microsoft Teams webhook URL in the text field.
4

Test and Save

Click Test to send a hello-world verification message to the Teams channel. Click Save to persist the configuration.

Disabling Teams Notifications

Click the toggle in the Notifications tab and confirm your choice. As with Slack, deactivating Teams notifications permanently removes the stored webhook URL.

What Each Notification Contains

Every notification sent by Gatling Enterprise Edition includes:
  • Simulation info summary — the simulation name, team, and run metadata
  • Run result — the final status (e.g., Successful, AssertionsSuccessful, AssertionsFailed, etc.)
  • Assertion results — individual pass/fail status for each configured assertion, if any
Notifications are sent once, immediately after a simulation run ends.

Security Notes

For data security:
  • Webhook URLs are ciphered before storage in the Gatling Enterprise Edition database.
  • Deactivating notifications permanently deletes the webhook URL — it is not retained in the database and must be re-entered if notifications are re-enabled later.
Store your webhook URLs in a safe location in case you need to re-configure notifications in the future.

Build docs developers (and LLMs) love