How to send only selected connectors logs to Application Insights/Log Analytics from Azure Logic App Standard workflow?

Question

Below are the Logic app standard logging configured:

Application Insights + Logic App Standard:

Logic app standard Host.json config:

{
	"version": "2.0",
	"logging": {
		"logLevel": {
			"default": "Warning",
			"Workflow.Host": "Warning",
			"Workflow.Operations.Runs": "Information",
			"Workflow.Operations.Actions": "Information",
			"Workflow.Operations.Triggers": "Information"
		},
		"applicationInsights": {
			"samplingSettings": {
				"isEnabled": true,
				"excludedTypes": "Request;Exception"
			}
		}
	},
	"extensionBundle": {
		"id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
		"version": "[1, 2.00]"
	},
	"extensions": {
		"workflow": {
			"Settings": {
				"Runtime.ApplicationInsightTelemetryVersion": "v2"
			}
		}
	}
}

Diagnostic Settings + Logic App Standard:

Linked a log analytics workspace to collect logs.

Test Workflow:

Issue:

Assume that a workflow contains 50 connectors, then per execution, almost 100+ rows of logs produced.

Logs produced for Run start, Run end, Trigger start, Trigger end, Each action start and end. By this way huge volume of logs sent to Log Analytics and Application Insights.

Refer below: (Logs for a single logic app workflow run)

Table : LogicAppWorkflowRuntime

Table: AppRequests

Question:

How to collect logs from only selected connectors? Example, in the above workflow, Compose connector has tracked properties. So I need to collect only logs from Compose connector. No information logs about other connector execution.

Referred Microsoft articles, but i didn't find other than above added Host.json config. By Log levels in Host.json config, only can limit particular category but not for each actions.

Any inputs or help would be much appreciated

Answer 1

@DIVIYAN S ,

Thanks for reaching out.Yes, your understanding is correct! In Azure Logic Apps Standard, logging is managed at a category level (e.g., Workflow.Operations.Actions, Workflow.Operations.Triggers) rather than at the individual connector level. This means that while you can adjust the log verbosity in host.json, you cannot selectively log specific connectors, such as the Compose action, while ignoring others.

Logging settings in host.json apply to broader categories, not individual actions.

No built-in way to log only specific connectors directly.

Alternative workaround: Send logs to Log Analytics and filter them using KQL queries.

Using Log Analytics to Filter Specific Connector Logs

Since Azure doesn’t provide fine-grained logging control per action, the best approach is:

1. Enable Diagnostic Settings to send logs to Log Analytics.
2. Use KQL (Kusto Query Language) queries to extract only relevant logs.

Example KQL Query: Retrieve Logs for "Compose" Action

AzureDiagnostics
| where ResourceType == "WORKFLOW" 
| where WorkflowName == "YourLogicAppName"
| where ActionName == "Compose"

Ref:

View and create queries for logic apps in Azure Monitor logs - Azure Logic Apps | Microsoft Learn