Controlling Diagnostic settings log levels for Logic App Standard

Dev S 91 Reputation points
2025-06-13T19:07:33.7466667+00:00

Is there a way to control the level of logs for the categories "LogicAppWorkflowRuntime" and "FunctionAppLogs" which are configured as Diagnostic Settings in Logic App Standard?

We are having a lot of entries generated in our Log Analytics and want to reduce the data ingestion to reduce costs. We already use AppInsights for our Logic App Standard, so, essentially, we would only need to see ERROR and CRITICAL messages through Diagnostics Settings messages in our Log Analytics.

For example, we do not need Information Level messages in the "FunctionAppLogs" Table, or every started and succeeded entry in the LogicAppWorkflowRuntime table.

Is there no way to control the level of logging and do we just turn off diagnostic settings instead?

Thanks.

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,542 questions
{count} votes

Accepted answer
  1. Chiugo Okpala 1,905 Reputation points MVP
    2025-06-13T21:47:13.3233333+00:00

    @Dev S welcome to the Microsoft Q&A community.

    You're right to be concerned about excessive log ingestion. It can quickly drive up costs. Unfortunately, Azure Logic Apps Standard does not currently provide a built-in way to filter logs by severity level within Diagnostic Settings. This means that logs for categories like "LogicAppWorkflowRuntime" and "FunctionAppLogs" will continue to generate all available levels, including informational messages.

    However, there are a few workarounds you might consider:

    Use Azure Monitor Logs queries: You can filter logs at the query level when analyzing data in Log Analytics, ensuring that only ERROR and CRITICAL messages are surfaced.

    • Route logs to a different destination: Instead of sending all logs to Log Analytics, you could direct them to Azure Storage or Event Hubs, where you can process and filter them before ingestion.
    • Disable Diagnostic Settings selectively: If certain log categories are unnecessary, turning off Diagnostic Settings for those specific categories might be the most effective way to reduce ingestion.

    For more details on monitoring and collecting diagnostic data for workflows, you can check out Microsoft's documentation on the topic.

    I hope these helps. Let me know if you have any further questions or need additional assistance.

    Also if these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.

    User's image


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.