Azure « rakhesh.com

Add multiple Azure VMs to a log analytics workspace for monitoring

Posted: September 26th, 2019 | Tags: log analytics | Category: Azure | §

I wanted to add a bunch of VMs in a subscription to a log analytics workspace in Azure so I can add it to update management etc. Didn’t find any command when I Googled for this, so here’s a blog post in case anyone else searches for it.

There isn’t anything fancy in what I am doing. The way to do it for a single VM is in this official doc. I just loop around it for all VMs.

# all VMs in the subscription (which you set via Set-AzContext)
$PublicSettings = @{ "workspaceId" = "" }
$ProtectedSettings = @{ "workspaceKey" = "" }

# Using -Status switch to get the status too
Get-AzVM -Status | Where-Object{ $_.Powerstate -eq "VM running" } | ForEach-Object { 
    $VMName = $_.Name
    $ResourceGroupName = $_.ResourceGroupName
    $Location = $_.Location
 
    Write-Host "Processing $VMName"

    Set-AzVMExtension -ExtensionName "MicrosoftMonitoringAgent" `
    -ResourceGroupName "$ResourceGroupName" `
    -VMName "$VMName" `
    -Publisher "Microsoft.EnterpriseCloud.Monitoring" `
    -ExtensionType "MicrosoftMonitoringAgent" `
    -TypeHandlerVersion 1.0 `
    -Settings $PublicSettings `
    -ProtectedSettings $ProtectedSettings `
    -Location "$Location"

}

# all VMs in the subscription (which you set via Set-AzContext)

$PublicSettings = @{ "workspaceId" = "" }

$ProtectedSettings = @{ "workspaceKey" = "" }

# Using -Status switch to get the status too

Get-AzVM -Status | Where-Object{ $_.Powerstate -eq "VM running" } | ForEach-Object {

$VMName = $_.Name

$ResourceGroupName = $_.ResourceGroupName

$Location = $_.Location

Write-Host "Processing $VMName"

Set-AzVMExtension -ExtensionName "MicrosoftMonitoringAgent" `

-ResourceGroupName "$ResourceGroupName" `

-VMName "$VMName" `

-Publisher "Microsoft.EnterpriseCloud.Monitoring" `

-ExtensionType "MicrosoftMonitoringAgent" `

-TypeHandlerVersion 1.0 `

-Settings $PublicSettings `

-ProtectedSettings $ProtectedSettings `

-Location "$Location"

}

Get the workspace ID and key from Log Analytics workspace > [your workspace] > Overview > “1. Connect a data source” > “Windows, Linux, and other sources”

ARM deployment – Accepting legal terms

Posted: July 7th, 2019 | Tags: arm templates | Category: Azure | §

I haven’t blogged for a while, I know. Except for a few movie posts it’s been pretty silent here. Mostly coz I have been too busy with work and never got a chance to blog. Plus now I use a note taking app (Bear) on my Mac to keep notes, so there’s less requirement for a blog to keep my notes.

I’ve been playing with ARM templates recently and came across the following when I was trying to deploy a Citrix NetScaler (or ADC as they call them now) today:

Azure Error: MarketplacePurchaseEligibilityFailed
Message: Marketplace purchase eligibilty check returned errors. See inner errors for details.
Exception Details:
Error Code: BadRequest
Message: Offer with PublisherId: citrix, OfferId: netscalervpx-121 cannot be purchased due to validation errors. See details for more information.[{“Legal terms have not been accepted for this item on this subscription: ‘xxxx’. To accept legal terms using PowerShell, please use Get-AzureRmMarketplaceTerms and Set-AzureRmMarketplaceTerms API(https://go.microsoft.com/fwlink/?linkid=862451) or deploy via the Azure portal to accept the terms”:”StoreApi”}]

To work around this login to the portal, click to create a new resource, search for “Citrix ADC”, select the one you are interested in deploying (from the drop down), then select “Get started”.

Then go ahead and enable it for all the subscriptions you are interested in. That’s all.

rakhesh.com

Search

Contact

Subscribe via Email

Subscribe via RSS/JSON

Categories

Recent Posts

Archives

Elsewhere

Add multiple Azure VMs to a log analytics workspace for monitoring

ARM deployment – Accepting legal terms