At TechEd Europe Microsoft officially announced Microsoft Azure Operational Insights. If you are not familiar with it check my previous posts about this new “tool”. Behind all these sexy dashboards there is also a very powerful search engine called “Search Data Explorer”. It uses a search window where you can enter a query to get any result you want / need.
The syntax of this query reminds a bit of PowerShell but it was specifically developed for Azure Operational Insights.
An example looks like this…
Microsoft offers already predefined queries for all installed Intelligence Packs, so you just need to pick the right one.
For example the Capacity Planning queries look like this…
But as always it is better to understand what is going on behind the scenes so that you can customize the result the way you want it. Daniele Muscetta (PM at Microsoft) as written excellent posts how you can build your queries and explains all the possible commands / syntax. You can find the posts here:
-
Azure Operational Insights Search How To: Part I – How to filter big data
-
Azure Operational Insights Search How To: Part IV – Introducing the MEASURE command
Daniele has written very detailed and long posts which is very useful at the beginning and after you get the idea you just need some sort of notes. For that reason I tried to summarize everything in one single cheat sheet so you can keep it on your desk for reference. It looks like this…
I hope it provides some help.
Download the PDF version from TechNet Gallery.
Update 6.11.2014 Version 1.1:
- Just eliminated some typos / changed some minor wording
Update 7.11.2014 Version1.2:
- Corrected field name Type is case sensitive
- Added new sample
- Formatting issues fixed
Great stuff! I’ll probably do another post – just to prove a point that the syntax is simple and you can learn it in a week, one post a day 🙂
Please could you fix the capitalization of field names? even Type should not be TYPE but Type – right now everything is case sensitive. Check out this idea in the backlog
http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519193-field-names-in-search-should-be-case-insensitive
Correction: only COMMANDS are case-Insensitive, but field names and values are SENSITIVE at this time.
Thank you Daniele! I fixed this issue in Version 1.2.