AzureRM.Insights

3.2.0

Microsoft Azure PowerShell - Insights service cmdlets for Azure Resource Manager

Minimum PowerShell version

3.0

Installation Options

Copy and Paste the following command to install this package using PowerShellGet More Info

Install-Module -Name AzureRM.Insights -RequiredVersion 3.2.0

Copy and Paste the following command to install this package using Microsoft.PowerShell.PSResourceGet More Info

Install-PSResource -Name AzureRM.Insights -Version 3.2.0

You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deploy all the dependencies to Azure Automation. Learn More

Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More

Owners

Copyright

Microsoft Corporation. All rights reserved.

Package Details

Author(s)

  • Microsoft Corporation

Tags

Azure ResourceManager ARM Insights

Cmdlets

Get-AzureRmUsage Get-AzureRmMetricDefinition Get-AzureRmMetric Remove-AzureRmLogProfile Get-AzureRmLogProfile Add-AzureRmLogProfile Get-AzureRmLog Set-AzureRmDiagnosticSetting Get-AzureRmDiagnosticSetting New-AzureRmAutoscaleNotification New-AzureRmAutoscaleProfile New-AzureRmAutoscaleRule Add-AzureRmAutoscaleSetting Get-AzureRmAutoscaleHistory Get-AzureRmAutoscaleSetting New-AzureRmAutoscaleWebhook Remove-AzureRmAutoscaleSetting Add-AzureRmMetricAlertRule Add-AzureRmLogAlertRule Add-AzureRmWebtestAlertRule Get-AzureRmAlertHistory Get-AzureRmAlertRule New-AzureRmAlertRuleEmail New-AzureRmAlertRuleWebhook Remove-AzureRmAlertRule

Dependencies

Release Notes

* Issue #4215 (change request) remove the 15 days limit in the time window for the Get-AzureRmLog cmdlet. Also minor changes to the unit test names.
* Issue #3957 fixed for Get-AzureRmLog
   - Issue #1: The backend returns the records in pages of 200 records each, linked by the continuation token to the next page. The customers were seeing the cmdlet returning only 200 records when they knew there were more. This was happening regardless of the value they set for MaxEvents, unless that value was less than 200.
   - Issue #2: The documentation contained incorrect data about this cmdlet, e.g.: the default timewindow was 1 hour.
   - Fix #1: The cmdlet now follows the continuation token returned by the backend until it reaches MaxEvents or the end of the set.<br>The default value for MaxEvents is 1000 and its maximum is 100000. Any value for MaxEvents that is less than 1 is ignored and the default is used instead. These values and behavior did not change, now they are correctly documented.<br>An alias for MaxEvents has been added -MaxRecords- since the name of the cmdlet does not speak about events anymore, but only about Logs.
   - Fix #2: The documentation contains correct and more detailed information: new alias, correct time window, correct default, minimum, and maximum values.

FileList

Version History

Version Downloads Last updated
5.1.6 0 3/22/2021
5.1.5 41 11/2/2018
5.1.4 13 9/17/2018
5.1.3 530 8/29/2018
5.1.2 13 8/24/2018
5.1.1 21 8/10/2018
5.1.0 176 7/27/2018
5.0.1 113 6/29/2018
5.0.0 183 5/1/2018
4.0.4 65 4/6/2018
4.0.3 34 3/23/2018
4.0.2 175 2/9/2018
4.0.1 493 1/26/2018
4.0.0 56 11/8/2017
3.4.1 5 10/12/2017
3.4.0 6 9/24/2017
3.3.1 7 8/16/2017
3.3.0 7 8/9/2017
3.2.1 6 7/18/2017
3.2.0 (current version) 7 7/11/2017
3.1.0 337 6/8/2017
3.0.1 23 5/24/2017
3.0.0 9 5/9/2017
2.8.0 13 4/5/2017
2.7.0 3 3/9/2017
2.6.0 5 2/22/2017
2.5.0 6 1/17/2017
2.4.0 6 12/14/2016
2.3.0 7 11/1/2016
2.2.0 5 9/27/2016
2.1.0 14 9/8/2016
2.0.1 10 8/10/2016
2.0.0 5 8/8/2016
1.0.11 5 7/11/2016
1.0.10 8 6/24/2016
1.0.9 6 6/1/2016
1.0.8 8 5/4/2016
1.0.7 97 4/18/2016
1.0.6 6 3/29/2016
1.0.5 6 3/4/2016
1.0.4.4 5 7/8/2017
1.0.4.3 7 3/14/2017
1.0.4.2 18 12/16/2016
1.0.4.1 13 9/8/2016
1.0.4 8 2/3/2016
1.0.3 6 1/12/2016
1.0.2 7 12/16/2015
1.0.1 9 11/9/2015
1.0.0 5 11/5/2015
0.10.0 3 10/8/2015
0.9.10 10 9/25/2015
0.9.9 4 9/24/2015
0.9.8 4 9/23/2015
Show less