Mithilesh Tiwari Welcome to Microsoft Q & A Community Forum.The "Search Result" property in your monitor alert JSON body typically appears when you have a metric alert rule configured to trigger based on a query or condition that uses Azure Monitor Logs (formerly known as Log Analytics) data. This property contains the query results when the alert condition is met. Kindly check if IncludedSearchResults
flag is set or not. This property indicates if the payload should contain the results.
Kindly also note alerts using the common schema have an upper size limit of 256 KB per alert. If the log alerts payload includes search results that cause the alert to exceed the maximum size, the search results aren't embedded in the log alerts payload. You can check if the payload includes the search results with the IncludedSearchResults
flag. Use LinkToFilteredSearchResultsAPI
or LinkToSearchResultsAPI
to access query results with the Log Analytics API if the search results are not included.
From information provided, I think that your prod alert rule is created using legacy log alerts api and the current one is being created using scheduledQueryRules API. Alert rules created with latest API only supports common schema and doesn't have the IncludedSearchResults
property within the schema. You can use dimensions to provide context to fired alerts and use LinkToFilteredSearchResultsAPI
or LinkToSearchResultsAPI
properties to access query results with the Log Analytics API. If you must embed the results, use a logic app with the provided links to generate a custom payload.
For more information on this, you can refer to below documents.