-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to app insight cluster using kql #1800
Comments
Same is the case for loganalytics (fails to connect), which has a URL for format - Data Source=https://ade.loganalytics.io/subscriptions/< sub-id >/resourcegroups/< rg-name >/providers/microsoft.operationalinsights/workspaces/< workspace -name >;Initial Catalog=NetDefaultDB;AAD Federated Security=True;Authority Id=< aad-tenant-name >;User=< user-fqdn > The stack is identical to the one above. |
I am seeing the same error when connecting to Log Analytics. Any workarounds or solutions available? |
@corivera Is there any update on this scenario? |
@JustinMDotNet would know more about the Kusto kernel. |
Hey @colombod , the Kusto extension doesn't support App Insights/Log Analytics (though it could with minor modifications). The way it was originally designed, a different library was used for querying those data sources called AzureMonitor. It's built into the Kusto extension but uses a deprecated Nuget package for its querying. |
Hi @JustinMDotNet I would love to put some effort into enabling this . Do you have any pointers to get me started with this? |
@JustinMDotNet is there any update coming? @Expecho is also willing to give this a go. Can we help him? |
Describe the bug
I am unable to connect to a app insights cluster using #!connect kql
Please complete the following:
Which version of .NET Interactive are you using? (In a notebook, run the
#!about
magic command. ):Version: 1.0.258004+3429f67626d2f15eec7d8f15a29215909284cb79
Screenshots
#!connect kql --kernel-name insights --cluster "https://ade.applicationinsights.io/subscriptions/<subscription>/resourceGroups/<resource-group>/providers/microsoft.insights/components/<app-insights-resource-name>" --database "<app-insights-resource-name>"
The text was updated successfully, but these errors were encountered: