Merge pull request #701 from MicrosoftDocs/main

12/3/2024 PM Publish

articles/azure-monitor/agents/azure-monitor-agent-extension-versions.md

@@ -11,14 +11,18 @@ ms.reviewer: JeffWo
 
 # Azure Monitor Agent extension versions
 
-> [!CAUTION]
-> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
 This article describes the version details for the Azure Monitor Agent virtual machine extension. This extension deploys the agent on virtual machines, scale sets, and Arc-enabled servers (on-premises servers with Azure Arc agent installed).
 
-We strongly recommended that you always update to the latest version, or opt in to the [Automatic Extension Update](/azure/virtual-machines/automatic-extension-upgrade) feature. You can expect automatic extension roll to take as long as 5 weeks after the initial release. You can expect any bug fix to be made in a future release. You can expect no servicing of existing releases.
+> [!Note]
+> The product group only supports Azure Monitoring Agent versions within the last 1 year. Customers should update to an agent version within this period.
+
+We strongly recommend that you always update to the latest version, or opt in to the [Automatic Extension Update](/azure/virtual-machines/automatic-extension-upgrade) feature. Automatic extension rollout follows standard Azure deployment practices to safely deploy the latest version of the agent. You should expect automatic updates to take weeks to rollout the latest version. Upgrades are issued in batches, so you may see some of your virtual machines, scale-sets or Arc-enabled servers get upgraded before others.
+
+
+> [!CAUTION]
+> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and planning accordingly. For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life).
 
-We strongly recommended to always update to the latest version, or opt in to the  feature. A version is not automatically rolled out until it meets a high quality bar which can take as long as 5 weeks after the initial release. 
 
 [//]: # "DON'T change the format (column schema, etc.) of the table without consulting glinuxagent alias. The [Azure Monitor Linux Agent Troubleshooting Tool](https://github.com/Azure/azure-linux-extensions/blob/master/AzureMonitorAgent/ama_tst/AMA-Troubleshooting-Tool.md) parses the table at runtime to determine the latest version of AMA; altering the format could degrade some of the functions of the tool."
 

articles/azure-monitor/agents/azure-monitor-agent-manage.md

@@ -251,8 +251,11 @@ N/A
 
 ## Update
 
-> [!NOTE]
-> The recommendation is to enable [Automatic Extension Upgrade](/azure/virtual-machines/automatic-extension-upgrade) to update installed extensions to the stable version across all regions. A version is not automatically rolled out until it meets a high quality bar which can take as long as 5 weeks after the initial release. Upgrades are issued in batches, so you may see some of your virtual machines, scale-sets or Arc-enabled servers get upgraded before others. If you need to upgrade an extension immediately, you may use the manual instructions below.
+> [!Note]
+> We strongly recommend that you always update to the latest version, or opt in to the [Automatic Extension Update](/azure/virtual-machines/automatic-extension-upgrade) feature.
+> Automatic extension rollout follows standard Azure deployment practices to safely deploy the latest version of the agent. You should expect automatic updates to take weeks to rollout the latest version.
+> Upgrades are issued in batches, so you may see some of your virtual machines, scale-sets or Arc-enabled servers get upgraded before others.
+> If you need to upgrade an extension immediately, you may use the manual instructions below. Only Agents released in the last year are supported.
 
 #### [Portal](#tab/azure-portal)
 

articles/azure-monitor/containers/container-insights-syslog.md

@@ -16,6 +16,8 @@ Container Insights offers the ability to collect Syslog events from Linux nodes
 - Port 28330 should be available on the host node.
 
 
+- Ensure hostPort functionality is enabled in the cluster. For example, Cilium Enterprise does not have hostPort functionality enabled by default and prevents the syslog feature from working.
+
 ## Built-in workbooks
 
 To get a quick snapshot of your syslog data, use the built-in Syslog workbook using one of the following methods: