Overview
Business Activity Monitoring deployment verification describes how to confirm that your BAM environment is correctly configured after initial setup. It provides a sample script that sends tracking events to the sample business process provisioned during deployment, so you can verify end-to-end data flow before configuring your own business processes.
Business value
Running the verification script immediately after deployment confirms that tracked data flows from your event source through the BAM processing pipeline and appears correctly in the Turbo360 portal. Catching configuration issues at this stage, before you build custom business processes, avoids debugging delays later in your rollout.
Prerequisites
Before running the deployment verification, ensure the following are complete:
- BAM environment deployment has been initiated and completed successfully.
- You have access to the Turbo360 portal and can view the BAM homepage.
- The sample business process, transaction, and transaction instances provisioned during deployment are visible in the portal.
Required permissions
You must be the Account owner or have Read access to Business Activity Monitoring to view tracked transaction instances in the portal.
How it works
During deployment, BAM provisions a sample business process with a pre-configured transaction. The verification script sends API requests that trigger the sample business process's start transaction and checkpoint stages. Due to a deliberate delay in the checkpoint logic, the start transaction event appears in the portal immediately, and the checkpoint events appear within approximately one minute.
Once the events appear in the portal, you have confirmed that:
- The BAM API endpoint is reachable from your environment.
- The processing pipeline is correctly writing tracked data to your SQL Database.
- The Turbo360 portal is reading and displaying tracking data as expected.
Steps
Use the following steps to verify your BAM deployment. Navigate to Business Activity Monitoring in the Turbo360 portal to locate the sample business process before running the script.
Run the verification script
Running the script against the sample business process produces transaction instances you can immediately inspect in the portal.
- Navigate to Business Activity Monitoring in the Turbo360 portal.
- Locate the sample business process created during deployment.
- Retrieve the BAM API endpoint and the sample business process tracking name from the portal or from the BAM Storage details section.
- Run the verification script, passing the BAM API endpoint and the sample transaction tracking name as parameters. Refer to 101 - Sending data to the BAM API for the script and full parameter reference.
- After running the script, return to the BAM portal and open the sample business process.
- Confirm that a new transaction instance appears with a Started status immediately.
- Wait up to one minute and refresh the view. Confirm that the checkpoint stages update to their expected completed states.
Troubleshooting
-
No transaction instance appears after running the script.
Cause: The BAM API endpoint is unreachable, or the tracking name passed to the script does not match the sample business process.
Fix: Verify the endpoint URL and tracking name. Confirm the deployed API Function App is in a Running state in the Azure portal. -
The start transaction event appears but checkpoint events never arrive.
Cause: The Processor Function App may not be running, or the Service Bus is not routing messages to the processor.
Fix: Check the Processor Function App status in the Azure portal. Review the Service Bus namespace for unprocessed messages. -
Transaction instance appears in a Failed or Exception state.
Cause: An error occurred during stage processing, often a misconfigured connection string or a SQL Database firewall rule blocking the Function App.
Fix: Review the Application Insights logs for the deployed Function Apps to identify the specific exception. Correct the configuration and re-run the script. -
The sample business process is not visible in the BAM portal.
Cause: Deployment did not complete fully, or the sample provisioning step failed.
Fix: Return to the BAM Getting started screen and check the deployment status. If deployment shows as complete but no sample process exists, re-initiate deployment or contact support. -
Script runs successfully but data is delayed beyond one minute.
Cause: High background job queue depth or a cold-start delay on the Function Apps.
Fix: Wait an additional two to three minutes. If data still does not appear, check the Function App logs for processing errors.