New Azure Monitor Agent attempts to consolidate all existing monitoring agents into one single agent. According to https://docs.microsoft.com/en-us/azure/azure-monitor/platform/azure-monitor-agent-overview, Log Analytics Agent is one the agents which is being replaced with new one. While new agent does indeed provide some log shipping capabilities, it does not implement all the features of the former agent. For example current Log Analytics Agent is also being used for other services, such as Changing Tracking and Update Management https://docs.microsoft.com/en-us/azure/azure-monitor/platform/log-analytics-agent#other-services and allows integration with Azure Automation. New agent seems does not mention anything about those features. Data Collection Rules only allow the shipment of system logs and performance counters, there is no mention of system update status.

I'm curious to know if new agent will attempt to fully replicate the features and functionality of current Log Analytics Agent and include Update Management in it's portfolio.

I have Azure monitor agent installed on a Ubuntu VM in Azure eastus and its not gathering performance counter data

root@markstestVM1205Thu:/var/log/azure# cat /etc/lsb-release DISTRIBID=Ubuntu DISTRIBRELEASE=18.04 DISTRIBCODENAME=bionic DISTRIBDESCRIPTION="Ubuntu 18.04.5 LTS" root@markstestVM1205Thu:/var/log/azure# uname -av Linux markstestVM1205Thu 5.4.0-1036-azure #38~18.04.1-Ubuntu SMP Wed Jan 6 18:26:30 UTC 2021 x8664 x8664 x86_64 GNU/Linux

I'm seeing the following error
root@markstestVM1205Thu:/var/log/azure# tail -f ./Microsoft.Azure.Monitor.AzureMonitorLinuxAgent/telegraf.log 2021-01-14T14:56:59Z E! [agent] Failed to connect to [outputs.socketwriter], retrying in 15s, error was 'dial unix /var/run/mdsd/defaultinflux.socket: connect: no such file or directory' 2021-01-14T14:57:14Z E! [telegraf] Error running agent: dial unix /var/run/mdsd/defaultinflux.socket: connect: no such file or directory 2021-01-14T14:57:32Z E! [agent] Failed to connect to [outputs.socketwriter], retrying in 15s, error was 'dial unix /var/run/mdsd/defaultinflux.socket: connect: no such file or directory' 2021-01-14T14:57:47Z E! [telegraf] Error running agent: dial unix /var/run/mdsd/defaultinflux.socket: connect: no such file or directory 2021-01-14T14:58:05Z E! [agent] Failed to connect to [outputs.socketwriter], retrying in 15s, error was 'dial unix /var/run/mdsd/defaultinflux.socket: connect: no such file or directory' 2021-01-14T14:58:20Z E! [telegraf] Error running agent: dial unix /var/run/mdsd/defaultinflux.socket: connect: no such file or directory 2021-01-14T14:58:38Z E! [agent] Failed to connect to [outputs.socketwriter], retrying in 15s, error was 'dial unix /var/run/mdsd/defaultinflux.socket: connect: no such file or directory' 2021-01-14T14:58:53Z E! [telegraf] Error running agent: dial unix /var/run/mdsd/defaultinflux.socket: connect: no such file or directory 2021-01-14T14:59:11Z E! [agent] Failed to connect to [outputs.socketwriter], retrying in 15s, error was 'dial unix /var/run/mdsd/defaultinflux.socket: connect: no such file or directory' 2021-01-14T14:59:26Z E! [telegraf] Error running agent: dial unix /var/run/mdsd/default_influx.socket: connect: no such file or directory

and
root@markstestVM1205Thu:/var/log/azure# tail -f ./Microsoft.Azure.Monitor.AzureMonitorLinuxAgent/extension.log 2021/01/14 15:44:54 ERROR:[Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Unable to start Telegraf service. Failed to start telegraf service. 2021/01/14 15:45:24 [Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Telegraf binary process is not running. Restarting telegraf now. Retry count - 1 2021/01/14 15:45:24 ERROR:[Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Telegraf service file does not exist. Failed to stop telegraf service: metrics-sourcer.service . 2021/01/14 15:45:24 ERROR:[Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Unable to start Telegraf service. Failed to start telegraf service. 2021/01/14 15:45:54 [Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Telegraf binary process is not running. Restarting telegraf now. Retry count - 1 2021/01/14 15:45:54 ERROR:[Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Telegraf service file does not exist. Failed to stop telegraf service: metrics-sourcer.service . 2021/01/14 15:45:54 ERROR:[Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Unable to start Telegraf service. Failed to start telegraf service. 2021/01/14 15:46:24 [Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Telegraf binary process is not running. Restarting telegraf now. Retry count - 1 2021/01/14 15:46:24 ERROR:[Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Telegraf service file does not exist. Failed to stop telegraf service: metrics-sourcer.service . 2021/01/14 15:46:24 ERROR:[Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.5.133] Unable to start Telegraf service. Failed to start telegraf service.

Currently, alert rules will fire when the condition(s) are met, even when the data for the lookback window is incomplete.

Here's an example:
An alert rule is configured for CPU Percentage > 90% with a 15-minute lookback window, splitting by VM resource dimension. A new VM is created with 100% CPU for the first minute, and the alert rule is evaluated at the end of the first minute. The alert rule currently triggers, even though there was only 1 minute worth of data (data is incomplete).

The desire here is to be able to configure whether the alert rule should fire in these cases where the data is incomplete.