In most cases when you are looking at the Alert Management Solution you do not care about the instances of an alert - especially if you have been notified by runbook/webhook/email.
I'd wager that most people care about the data in the search query that caused that alert and the data it returned. Having to copy and paste the LinkToSearchResults is quite time consuming. The UX on this should be improved to allow jumping directly to the search results that caused the alert, would save time on training too!
LinktoResults property is now clickable in e-mail notifications and users can get details on alert firings in UI via Enhanced Unified Alerts in Azure: https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-overview-unified-alerts#enhanced-unified-alerts-public-preview
Sending a crisp email which doesn't flood your inbox or mobile device - while providing necessary alert details, is a hard act to balance. We have tried to keep the email limited and focused - suitable for non-Power users, with top results included in email and additionally link to query result.
For Power/DevOps users, like yourself, we give the option of using Webhooks and Runbooks from Alerts - to post the data to your own Azure Automation logic, Tool or Communication App like MS Teams or Slack. Using Webhook integration, you can push alert details to say Slack and just click the Search Results link to get results; or turn it to 11, by have Azure Automate run a runbook to analyze the results and auto-remediate.
More info on Webhooks & Runbook support here: https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-alerts-actions
Whoops - didn't know my search term would end up as the title.
Stanislav Zhelyazkov commented
Please make LinktToSearchResults value a clickable URI. It is very hard to copy the URI via the interface it always adds it to the search field when you try to copy it