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.

Automatic resource identification

  • 3 minute(s) read
Prev Next

Overview

Automatic resource identification lets Business Activity Monitoring (BAM) detect and display the Azure resource that executed each transaction stage — without requiring manual entry on every tracking call. When a transaction instance is triggered, BAM identifies the execution source and shows the corresponding resource type icon in the message flow, giving you immediate visual context for where each stage ran.

Business value

Knowing which resource executed a transaction stage speeds up incident diagnosis — instead of correlating logs across multiple Azure services, you can see the execution source directly in the BAM message flow. For teams running complex integrations across Logic Apps, Power Automate, Azure Functions, and APIM, this eliminates a significant manual investigation step when tracing failed or delayed transaction instances.

How it works

BAM identifies the execution source from the Executed at value configured on each transaction stage. There are two ways this value is resolved:

Automatic identification applies when the transaction instance is triggered by a Logic App, Power Automate, or Custom API. BAM detects the source automatically and displays the corresponding resource type icon in the message flow — no additional parameter is required.

Manual identification applies when the transaction instance is triggered by an Azure Function, APIM, or another resource type not covered by automatic detection. In these cases, the resource icon displayed in the message flow is determined by the value passed in the BAM-ExecutedAt parameter on the tracking call. You must supply a meaningful value — for example, pass azure function when triggering from an Azure Function — so that BAM can match it to the correct icon.

If the BAM-ExecutedAt parameter is left blank for these resource types, BAM falls back to the Executed at dropdown value configured in the transaction stage designer.

Steps

Configure the execution source for a transaction stage from the transaction designer in BAM.

Set the Executed at value for a stage

Specifying the Executed at value on a stage tells BAM which resource type icon to display in the message flow when that stage is executed.

  1. Navigate to Business Activity Monitoring > Business Process > Transactions.
  2. Open the transaction and select the stage to configure.
  3. In the stage editor, locate the Executed at dropdown.
  4. Select the resource type that executes this stage: Logic App, Power Automate, Custom APIs, Azure Function, APIM, or Others.
  5. Click Save.

For Azure Function, APIM, and Others, also pass the BAM-ExecutedAt parameter in your tracking call with a value that matches the resource type — for example, azure function. This ensures the correct icon appears in the message flow regardless of the fallback configured in the stage designer.

Troubleshooting

  1. Resource type icon is not appearing in the message flow
    Cause: The BAM-ExecutedAt parameter was not passed in the tracking call, and the stage's Executed at value is not set.
    Fix: Set the Executed at value in the stage editor, or pass a meaningful BAM-ExecutedAt value in the tracking call.
  2. The wrong resource icon is displayed for an Azure Function, APIM, or custom resource
    Cause: The BAM-ExecutedAt parameter value does not match the expected resource type label — for example, passing function instead of azure function.
    Fix: Update the BAM-ExecutedAt parameter value to match the resource type label exactly, such as azure function or apim.
  3. BAM is showing the fallback icon instead of the expected resource icon
    Cause: The BAM-ExecutedAt parameter was left blank on the tracking call, so BAM fell back to the Executed at dropdown value from the stage designer.
    Fix: Pass a meaningful value in BAM-ExecutedAt on every tracking call where the execution source should override the stage designer setting.
  4. The Executed at dropdown is missing from the stage editor
    Cause: The stage was created before automatic resource identification was introduced, or the transaction uses a deployment type that does not support this setting.
    Fix: Edit the stage and check for the Executed at field. If absent, verify the business process uses a Custom Logging type transaction. If the field is still not visible, the stage may need to be recreated after upgrading to a version that includes automatic resource identification.
  5. The resource icon appears correctly in the stage designer but not in the message flow
    Cause: The tracking call is passing a BAM-ExecutedAt value that overrides the stage designer setting with an unrecognised value.
    Fix: Check the BAM-ExecutedAt parameter value in the tracking call and correct or remove it so the stage designer value is applied as the fallback.

Related articles