Forum Discussion
MicrosoftHow to programmatically generate a link to open an App Insights KQL query?
joruales Maybe a bit late, but as you probably noticed, a URL generated from "Copy Link to Query" has the following format:
https://portal.azure.com/#@TENANT_ID/blade/Microsoft_Azure_Monitoring_Logs/LogsBlade/resourceId/%2Fsubscriptions%2FSUBSCRIPTION_ID%2FresourceGroups%2FRESOURCEGROUP%2Fproviders%2Fmicrosoft.insights%2Fcomponents%2FAPPINSIGHTSINSTANCENAME/source/LogsBlade.AnalyticsShareLinkToQuery/q/ENCODEDSTRING/timespan/TIMESPAN
The ENCODEDSTRING is your query zipped and URL encoded/escaped. You must use this approach when the query has more than 1600 characters. Otherwise, if your query has less than 1600 characters, you can replace the q parameter by a query parameter and the encoded string will simply be your query URL escaped. For instance:
https://portal.azure.com/#@TENANT_ID/blade/Microsoft_Azure_Monitoring_Logs/LogsBlade/resourceId/%2Fsubscriptions%2FSUBSCRIPTION_ID%2FresourceGroups%2FRESOURCEGROUP%2Fproviders%2Fmicrosoft.insights%2Fcomponents%2FAPPINSIGHTSINSTANCENAME/source/LogsBlade.AnalyticsShareLinkToQuery/query/availabilityResults%20%7C%20where%20duration%20%3E%20500%20%7C%20take%201/timespan/TIMESPAN
would open your App Insights instance with the following query:
availabilityResults| where duration > 500| take 1
hspinto Thanks again for the reply. My question may be silly.
Not sure what zip means. Can we zip from client side i.e., from javascript / angular?
Is encode mean encodeURI() method from javascript?
Any help by providing sample code to zip and encode from javascript / angular would be really helpful.
The reason for seeking this help is I need to prepare query dynamically and open Application Insights Instance from Angular. Please help me in this regard.
Thank you in Advance!
Microsoftkrishnachandar, I am not a Javascript expert nor I have any code sample to share with you. But you can for sure zip from client side, as there are many libraries out there to perform that. I would however recommend you to first analyze the Azure portal Javascript code itself. When you click on the "Link to query" button, everything happens on the client side. If you manage to understand how that button click event is captured and processed, you'll for sure find the answer to your question in the event processor code itself.