In August 2017 Microsoft released a new query language for Log Analytics which will be the default query language as of late October (*see the graphic below for the message you get if you haven’t upgraded your workspace yet*).

With this change, all blog posts which I have written about Log Analytics prior to that release which had contained the older query language have been deprecated, updated or replaced. I have reviewed and taken steps for all of my historical blog posts related to OMS which are listed below.

This blog post should serve two purposes:

  1. To provide a quick index of all blog posts which I have done related to Log Analytics which include sample queries.
  2. To show a quick way to convert other examples of the old query language – wherever you find them.

Log Analytics related blog posts with query samples:

The following posts already have the new query language:

Top 10 tips to maximize the benefits of your Log Analytics workspace by minimizing non-required data

The following have been replaced with an updated blog posts:

The Server and Client performance solution or OMS:

Original blog post: https://www.catapultsystems.com/cfuller/archive/2016/11/21/the-server-and-client-performance-solution-for-oms/

The following blog posts have been updated:

The new way to get data from Log Analytics into Power BI

Configuring Power BI to regularly update data

Using the free tier data consumption tracker for larger environments

Adding weather forecasting information to OMS

How to visualize Windows and Unix system performance in OMS

Using OMS to perform synthetic web transactions

Knowing what your Windows Media Center is up to from anywhere

Visualizing Azure Automation job information in Microsoft OMS

Using search in OMS to identify what is assessed in the SQL assessment

Using the View Designer in Microsoft OMS

Using Power BI and OMS to visualize event and alert information

Using Power BI and OMS to visualize performance information

Gotchas while using OMS for server key performance indicators

What could server health monitoring look like in OMS

Fun with OMS and Windows Media Center


The following blog post have been deprecated:

The old way to get data from Log Analytics into Power BI: https://www.catapultsystems.com/cfuller/archive/2016/03/29/using-power-bi-and-oms-for-security-dashboards-and-reports/

Server health visualization has been covered better with the new pre-built solution available here.

https://www.catapultsystems.com/cfuller/archive/2016/02/10/using-oms-to-visualize-server-health-based-on-processor-utilization/

https://www.catapultsystems.com/cfuller/archive/2016/02/08/using-oms-to-visualize-server-health-based-on-free-disk-space/

https://www.catapultsystems.com/cfuller/archive/2016/02/04/using-oms-to-visualize-server-health-based-on-memory-utilization/

https://www.catapultsystems.com/cfuller/archive/2016/01/29/approaches-available-to-provide-heartbeat-alerts-in-oms/

https://www.catapultsystems.com/cfuller/archive/2016/01/28/notifying-when-a-server-is-offline-based-on-operations-manager-event-log-entries/

https://www.catapultsystems.com/cfuller/archive/2016/01/26/notifying-when-a-server-is-offline-based-on-when-agents-last-added-data-to-oms/

How to convert the original query language into the new one:

Until these blogs posts can be converted (or replaced or deprecated), you can use the following approach to take the original query language and convert it to the new one:

  1. Copy the existing query language into Log Search.
  2. Choose the option to “Show legacy language converter”

  3. Paste the original query in (such as the simple * query which converted to “search *”) and choose the option to convert the query.

This approach will provide a quick workaround for the majority of queries which still exist from the original language in my blog or other sources.

Summary: This blog post details blogs which I have written that include Log Analytics queries. If you find additional changes which would be useful or blog posts which I missed please reply with a comment to this blog post. If you need to use deprecated posts which include the original query language, use the steps shown in this blog post to convert them to the new query language.