• Simple yet powerful. Easier to understand, and similar to SQL with constructs like a natural language.
• Full piping language. Extensive piping capabilities, where any output can be piped to another command to create complex queries.
• Search-time field extractions. With calculated fields at runtime, you can use complex calculations for extended fields, and then use them for additional commands including joins and aggregations.
• Advanced joins. Ability to join tables on multiple fields by using inner and outer joins, and join on extended fields.
• Date/time functions. Greater flexibility because of advanced date and time functions.
• Smart Analytics. Advanced algorithms to evaluate patterns in data sets and compare different sets of data.
• Learn more about the new query language.

Changes to be aware of after you upgrade

• My dashboard is being deprecated, in favor of View Designer and Azure Dashboards. Existing tiles become read-only.
• Power BI integration is replaced with a new process. Any existing schedules will be disabled.
• Azure Resource Manager templates can be used to create and configure Log Analytics workspaces. The versions of the upgraded API and examples of tasks you can perform are available here.
• Alert actions using webhooks and runbooks will need to be updated to conform to a different response format. You can see a sample payload in the Alert actions article.
• Log Search API and PowerShell Cmdlet are being deprecated on December 31, 2017. Any use of the Log Search API and the Get-AzureRmOperationalInsightsSearchResults Cmdlet should be migrated to the Azure Log Analytics REST API and the Invoke-LogAnalyticsQuery PowerShell Cmdlet. You can do so by using the new query language.

Upgrade rollout schedule

• New workspace creation (week of October 16, 2017). New workspaces are created with the new Log Analytics language. You cannot create legacy workspaces using the legacy language.
• Automatic workspace upgrade (starting the week of October 30, 2017). We start rolling out automatic workspace upgrades—all workspaces that haven't been upgraded will be automatically upgraded to the new Log Analytics language. This process will be gradual per region, and carried out in this order:

Already upgraded?

Additional resources 

• New and improved Log Analytics announcement
• Azure Log Analytics query language
• Known issues and FAQs
• Log Analytics documentation
• How to upgrade

• Centralize and correlate millions of logs from containers at scale in the cloud.
• See real-time metrics on CPU, memory, storage, network usage, and performance for containers and nodes.
• Identify containers that consume excess resources on a host.
• Monitor resource usage on a per-process level (Docker container top).
• View overall container node inventory, which includes orchestration information.

Azure Resource Manager template for seamless installation with Service Fabric

How do I try this?

How can I give you guys feedback?

• UserVoice: Post ideas for new Azure Log Analytics features to work on. Visit the UserVoice page.
• Forums: Visit the Azure Log Analytics Forums.
• Email: Tell us whatever is on your mind by emailing us at OMScontainers@microsoft.com.

samis@31e9b19155c3:/# kubectl get nodes
Name                    Status    Age       Version
3830dacs9000            Ready     19d       v1.6.6-9+8a67b481dfc2c6
3830dacs9001            Ready     19d       v1.6.6-9+8a67b481dfc2c6
k8s-master-3830dc00-0   Ready     19d       v1.6.6

• Security data collection, search, and analysis 
• Notable events driven by predefined and custom queries 
• Security assessment dashboards, including system update status, antimalware protection state, OS baseline configurations, and identity and access 
• Inventory of connected computers 
• Advanced threat detection 
• Interactive threat intelligence map 

• Security policies to ensure compliance with company and regulatory security standards 
• Actionable security recommendations to help mitigate security vulnerabilities 
• Automatic discovery and monitoring of new Azure resources 
• Additional security assessments for Azure services, including monitoring of VM, network, storage, and SQL configurations 
• Adaptive application and just in time access controls for Azure virtual machines 
• Security incidents and streamlined investigation for rapid threat response 

• Distribution of failed jobs across VMM instances to easily scope down the broken instances.
• Distribution of failures over time to find sudden spikes, and to help with correlating the cause and failures.
• Distribution of failed jobs and errors to help with identifying the most error-prone jobs and the cause.
• Distribution of the job runtime across different runs to identify the sluggish and error-prone jobs.

• Bring together the jobs data from multiple VMM instances to a single OMS workspace. With a view, now you can keep an eye on job details for all your VMM instances together.
• Configure your OMS alerts with VMM jobs information to raise notifications for completion or failure of VMM jobs, and inform the appropriate teams.
• Correlate VMM job data with other events in OMS log analytics for faster troubleshooting of failures. You can easily identify the possible causes of sudden failures on a VMM machine by correlating the VMM job logs with information from solutions like Change Tracking and Hyper-V management solutions.
• Use Azure Automation runbooks with VMM job data to help enable automatic remediation for known or frequent issues.

• Get a free trial of OMS.
• Deploy an Azure template for easy installation.
• Share feedback and tell us whatever is on your mind.
• Contribute (optional). It’s an open-source solution, so feel free to try it out and to contribute enhancements and ideas on GitHub (whenever possible).

$ExtPublisher = "Microsoft.Azure.Monitoring.DependencyAgent"

$OsExtensionMap = @{ "Windows" = "DependencyAgentWindows"; "Linux" = "DependencyAgentLinux" }

$rmgroup = "<Your Resource Group Here>"

Get-AzureRmVM -ResourceGroupName $rmgroup |

ForEach-Object {

""

$name = $_.Name

$os = $_.StorageProfile.OsDisk.OsType

$location = $_.Location

$vmRmGroup = $_.ResourceGroupName

"${name}: ${os} (${location})"

Date -Format o

$ext = $OsExtensionMap.($os.ToString())

$result = Set-AzureRmVMExtension -ResourceGroupName $vmRmGroup -VMName $name -Location $location `

-Publisher $ExtPublisher -ExtensionType $ext -Name "DependencyAgent" -TypeHandlerVersion $version

$result.IsSuccessStatusCode

}

• UserVoice: Post ideas for new OMS features to work on. Visit the OMS UserVoice page.
• OMS Forums: Good general discussion of OMS. Visit the OMS Forums.
• Email: Tell us whatever is on your mind by emailing us at OMScontainers@microsoft.com.