@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.