Forum Discussion
Querying ApplicationInsights
Devin,
If you're querying exclusively Application Insights, please use option 3 (querying from within Application Insights).
If you're querying a combination of Log Analytics and Application Insights, please use option #1 from within either the AI or LA portals. IntelliSense support is something high on our backlog, together with a better unification between the two services. Expect to see features around this in the coming months.
Option 2 should be considered outdated. I'd turn off the Application Insights connector to both avoid the schema confusion, as well as save yourself some costs from dual-ingesting the data. This feature was originally created as a stop-gap before we had cross-AI-and-LA queries available.
- DeletedJul 17, 2018
Hello,
How would I write the query if I wanted to use it for azure alerts, to query though dependencies? I'm currently trying option one listed above, but it is returning an error.- pavan kumarJul 18, 2018Copper Contributor
Looks like the data is not been captured in the LA from the VM, please check the following:
1. Check if the data is been captured in LA, try with the basic queries to see the data.
2.Agent is properly installed ? if not try to reinstall it in the VM.
3. Check the Internet connectivity in the VM to communicate also port 443 should be opened as by default the internet access is restricted.
Hope this should give help you.
- DeletedJul 18, 2018
The query is working fine in log analytics, and the data is definitely there, but it is still throwing in error, that states: Query syntax error.
app("Sitecore Production").dependencies
|where
target !contains "brightcove"
and target !contains "sitecore1.maxmind.com"
and target !contains "lkqd"
|summarize
Failure_rate= ((sum(iif(success=="True", 0, 1 ) )+0.00000)/ count()) * 100,
failures=sum(iif(success=="True", 0, 1 ) ),
total=count()
by target, bin(timestamp,1h)
|where Failure_rate > 50
This is the query I am trying to run.
Looking at the first comment, It looks like we were relying on method #2, but seems to be no longer viable.