Documentation Index

Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt

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

Environment setup

  • 4 minute(s) read
Prev Next

Overview

This article walks you through the initial setup of a Business Activity Monitoring (BAM) environment using the Custom Logging (Push Model) type.

During setup, you choose a deployment model — either Turbo360-hosted infrastructure or your own Azure subscription — and provide the connection details BAM needs to store and process your business data.

Business value

A correctly configured BAM environment is the foundation for all business process tracking. Completing this setup deploys the BAM infrastructure, creates a sample Business Process and Business Transaction, and makes the environment immediately available for instrumentation. Choosing the right deployment model at this stage determines where your business data is stored and who controls it.

Prerequisites

Before you begin, confirm the following:

  • You have access to the Turbo360 portal and can reach the BAM Get Started flow from the homepage.
  • You have decided on a deployment model: Use Turbo360 infrastructure or Use your Azure subscription (see Deployment details for a comparison).
  • If using Turbo360 infrastructure: you have the connection strings for an Azure SQL Database and an Azure Storage Account within your own Azure subscription.
  • If using your Azure subscription: you have a service principal with the required permissions, and you know the resource group name and region where BAM resources will be deployed.

Required permissions

You must hold the Account owner role in Turbo360 to initiate a BAM environment deployment.

How it works

The BAM setup wizard guides you through three stages: selecting the tracking type, choosing a deployment model, and providing infrastructure credentials. Once you click Initiate deployment, Turbo360 provisions the BAM resources and creates a sample Business Process and Business Transaction so you can explore the product immediately.

The two deployment models differ in where the event processing infrastructure lives:

  • Use Turbo360 infrastructure — BAM event processing is hosted by Kovai. You supply your own Azure SQL Database and Azure Storage Account connection strings so that your business data remains within your control.
  • Use your Azure subscription — All BAM infrastructure is provisioned directly into your Azure subscription. You retain full ownership of every resource.

Steps

Use the following steps to set up a new BAM environment using the Custom Logging type. Start from the Turbo360 homepage and click Get Started on the Business Activity Monitoring card.

  1. Choose Custom Logging type and click Next.
  2. Select your preferred deployment model from the available options.

Use Turbo360 infrastructure

Select this option when you want BAM event processing hosted by Kovai while keeping your business data in your own Azure storage resources.

  1. Select Use Turbo360 infrastructure and click Next.

  2. Enter a group name to organise your Business Processes within this group.

  3. Provide the SQL Database connection string and the Storage Account connection string, then click Validate.

  4. After successful validation, click Initiate deployment.

    Turbo360 provisions the BAM environment and deploys a sample Business Process and Business Transaction. The deployment screen shows learning resources while the deployment is in progress.

Use your Azure subscription

Select this option when you want all BAM infrastructure provisioned directly into your own Azure subscription.

  1. Select Use your Azure subscription and click Next.

  2. Enter a group name to organise your Business Processes within this group.

  3. Provide and validate your service principal credentials, then click Next.

  4. Enter the resource group name and select the region where BAM resources will be deployed.

  5. Choose the service and pricing tiers for each required resource.

  6. Click Initiate deployment.

    Turbo360 provisions the BAM environment into your Azure subscription and deploys a sample Business Process and Business Transaction. The deployment screen shows learning resources while the deployment is in progress.

Troubleshooting

  1. Validation fails for the SQL Database or Storage Account connection string
    Cause: The connection string is malformed, the resource does not exist, or the credentials have insufficient permissions.
    Fix: Verify the connection string format in the Azure portal. Confirm the SQL Database and Storage Account exist and that the credentials have at least read/write access. Re-enter the corrected string and retry validation.

  2. Validation fails for the service principal
    Cause: The Tenant ID, Client ID, or Client Secret is incorrect or expired, or the service principal lacks the required Azure permissions.
    Fix: Confirm the service principal credentials in the Azure portal. Ensure the secret has not expired and the principal has the permissions required for BAM deployment. Re-enter the values and retry.

  3. Initiate deployment button is not available after validation
    Cause: One or more required fields have not been validated successfully.
    Fix: Review each field on the current setup step. All fields must show a successful validation state before the Initiate deployment button becomes active.

  4. Deployment fails partway through
    Cause: Insufficient quota, missing permissions, or a resource naming conflict in the target Azure subscription.
    Fix: Check the Azure activity log for the resource group to identify the failing resource. Confirm your subscription has sufficient quota for the selected service tiers and that the deploying identity has Contributor access to the resource group.

  5. Deployment completes but no sample Business Process is visible
    Cause: The deployment succeeded but the portal has not refreshed to reflect the new environment.
    Fix: Refresh the BAM module in Turbo360. If the sample Business Process is still absent after a full page reload, navigate to Business Processes and confirm the group created during setup is visible.

Related articles