Azure Monitor
Azure Monitor Action Groups enable you to configure how to receive notifications when an Azure Monitor Alert is triggered.
-
Azure network performance monitor keeps sending the packets to the deallocated VM.
Azure Network Performance Monitor keeps sending the test packets to the deallocated VMs and causes the false alert issue. Since the VM is shut down and will not respond to the test traffic, the packet loss ratio of the subnet link will be marked as 100% while there's no network performance issue. It would be best if Azure adjusts the NPM and make sure deallcated VMs will not get any test packets.
1 vote -
enable custom log in container
There is no way to collect custom log on container. In order to collect various kinds of log files on containers, We strongly desire to add this feature to Azure Monitor.
6 votes -
Enable setting VM Insights Health default configurations at scale
VM Insight Health default configuration for monitors can't be directly changed (https://docs.microsoft.com/en-us/azure/azure-monitor/insights/vminsights-health-configure-dcr). Overrides can only be defined in the monitor configuration for individual virtual machines. To make the solution scalable, we need to both change the defaults and apply overrides to groups/scopes, not individual computers.
1 vote -
Make File Share dimension available for monitoring the standard storage accounts
This dimension is only available for premium storage accounts, which in turn, have their own functional restrictions. It should not be asking too much to expect that the file share dimension be made available to be monitored separately.
As of now, the work-around is to create separate storage accounts for each share, in order to monitor each such share separately.
I had a case open with Microsoft support regarding this. Please see the case reference: REG:121011024000358
1 vote -
Azure Monitor Agent performance counters collection on Ubuntu 18.04 Vms not working
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…1 vote -
Activate Azure Monitor for AKS without collecting container STDOUT logs in Azure Analytics Workspace
It would be nice to activate Azure Monitor for AKS without collecting container STDOUT logs in Azure Log Analytics, I usually only use the Live Log feature, meanwhile the size of the logs in Azure Log Analytics keep increasing and therefore the price. If I could activate Azure Monitor, see my container stdout logs with the Live Log feature and do not collect the logs in Azure Log Analytics Workspace that'll be great.
1 vote -
Azure Storage capacity metrics update hourly
Azure storage metrics are only refreshed daily (every 24 hours) even though they are sent hourly. https://docs.microsoft.com/en-us/azure/storage/blobs/monitor-blob-storage-reference#capacity-metrics
This means that any alert configured on capacity metrics may trigger up to 24 hours after the threshold has been breached.Please change it to be refreshed hourly
2 votes -
Add support for VM Insights in South Africa North and West
Please advise when VM Insights will be available for Virtual Machines and Log Analytics Workspaces hosted in South Africa North and West. This is a feature that many clients want for full monitoring and don't want to have to send their data cross-region.
1 vote -
Deleting a VM's Data Collection Rule Association doesn't stop it logging to a log analytics workspace
Adding a Virtual Machine as a "resource" to a Data Collection Rule creates a Data Collection Rule Association, which triggers an install of the Azure Monitor Agent, which allows logs to be sent to the associated logs analytics workspace.
On removing the VM as a resource on the Data Collection Rule, it would be expected that logs would stop appearing in the logs workspace from that VM, however the logs continue to appear. This seems like a bug.
mdsd is responsible for sending the logs, and should receive updated configuration when the VM is removed from the Data Collection Rule…
1 vote -
Allow Export or move of Log Analytics Workspace to different Region/Workspace
Allow the export of a log analytics workspace into a different log analytics workspace in another region. Currently, log analytics workspaces cannot be migrated to different regions. Due to feature differences in regions this can become a difficult issue to resolve if a feature that was not an initial requirement becomes a requirement after the fact. Due to the changing landscape of needs and desires over time, deleting a log analytics workspace after incredible investment can become a roadblock. Ideally, the ability to move a log analytics workspace from one region to another would be a fantastic feature.
1 vote -
Add Network Watcher capabilities and/or features to Kubernetes Monitoring
Give Kubernetes more in-depth networking power via the Azure Portal such as the addition of Network Watcher's traffic monitoring capabilities and/or features to it.
1 vote -
Diagnostic settings not being a part of a Resource Group
Currently diagnostic settings are not a part of a resource group in Azure, this is uncommon and was wondering if there are plans to move these settings into a RG like most other resources.
In the case of our use, we use terraform to provision these onto app services and azure SQL, which are by definition regional. I think it makes sense for diagnostic settings to follow this methodology.
The issue we face is when destroying RG's the settings are not taken out, we need to run adhoc scripts to remove them.
1 vote -
Allow more intelligent auto-scale (scale in) for virtual machine instances
Azure auto-scale is metric driven. Can it be expanded to allow smarter scaling in to prevent removal of a server that is busy doing work?
E.g. can a scale-in policy be defined to scale-in based on the standard metrics of CPU/RAM etc. but to also check if the server is busy. This could be done by supporting a webservice call or executing a run-book or other to check status.
It would save having to emit a custom metric from the servers, whose only purpose would be to indicate 'I'm busy - don't scale me in'.1 vote -
Azure Monitor Agent (Linux) stopped logging to logs workspace
We have Linux VMs with Azure Monitor Agent installed (via adding the VM to a Data Collection Rule).
Logs stopped appearing in the logs workspace from one VM (others continued to log to the workspace).
Neither a reboot of the VM nor restarting mdsd restored the logging to the workspace.
We got logs:
[DAEMON] Error: unexpected user id 0. Do nothing.
[DAEMON] START mdsd daemon ver(1.5.133) pid(12673) uid(0) gid (0)
[/source/external/WindowsAgent/src/shared/mcsmanager/lib/src/RefreshMSIToken.cpp:214,RefreshMsiTokenThreadProc]Failed to connect to any resolved endpoint ErrorCode:...
[/source/external/WindowsAgent/src/shared/mcsmanager/lib/src/RefreshMSIToken.cpp:214,RefreshMsiTokenThreadProc]Failed to connect to any resolved endpoint ErrorCode:...
[/source/external/WindowsAgent/src/shared/mcsmanager/lib/src/RefreshMSIToken.cpp:193,RefreshMsiTokenThreadProc]Failed to get MSI token from Azure IMDS: Failed to get MSI token from…1 vote -
Linux Syslog Data Source filtering doesn't take effect.
Azure Monitor Agent on a Linux VM doesn't filter logs according to log level on the corresponding data collection rule.
Each log facility has a minimum log level in the Data Collection Rule Data Source.
We observe:
Minimum Log Level "None": No logs from that facility appear in workspace
Minimum Log Level not "None": All logs from that facility appear in workspacee.g. if LOG_LOCAL0 is set to LOG_ERR we continue to get lower log levels (e.g. LOG_DEBUG) from that facility in the logs workspace.
1 vote -
Linux Load Average
Is it feasible to include the load averages from Linux servers as an available performance counter?
1 vote -
Please support the "User App for Microsoft OMS Integration" for PAris version of ServiceNnow
Please support the "User App for Microsoft OMS Integration" for PAris version of ServiceNnow
1 vote -
Please support the "User App for Microsoft OMS Integration" for PAris version of ServiceNnow
Please support the "User App for Microsoft OMS Integration" for PAris version of ServiceNnow
1 vote -
Provide API to list alert history of new alerts
Provide an API to allow to list history of alerts raised and be able to filter by SCOPE filter.
Actually we can list of alerts raised but it list only classic alerts :
Get-AzAlertHistory -StartTime 2020-10-30T11:00:00 -EndTime 2020-11-11T12:00:0012 votes -
+385923562906
sta zoves kad sam reka da je gotovo
1 vote
- Don't see your idea?