Konfiguracja metryk niestandardowych dla stopniowych aktualizacji w zestawach skalowania maszyn wirtualnych

Użyj polecenia az vmss extension set , aby dodać rozszerzenie kondycji aplikacji do definicji modelu zestawu skalowania.

Utwórz plik JSON o nazwie extensions.json z żądanymi ustawieniami.

{
  "protocol": "<protocol>",
  "port": <port>,
  "requestPath": "</requestPath>",
  "gracePeriod": <healthExtensionGracePeriod>
}

Zastosuj rozszerzenie kondycji aplikacji.

az vmss extension set \
  --name ApplicationHealthLinux \
  --publisher Microsoft.ManagedServices \
  --version 2.0 \
  --resource-group myResourceGroup \
  --vmss-name myScaleSet \
  --settings ./extension.json

Uaktualnij maszyny wirtualne w zestawie skalowania. Ten krok jest wymagany tylko wtedy, gdy zestaw skalowania korzysta z zasad ręcznego uaktualniania. Aby uzyskać więcej informacji na temat zasad uaktualniania, zobacz temat Upgrade policies for Virtual Machine Scale Sets (Zasady uaktualniania dla zestawów skalowania maszyn wirtualnych)

az vmss update-instances \
  --resource-group myResourceGroup \
  --name myScaleSet \
  --instance-ids "*"

Użyj polecenia cmdlet Add-AzVmssExtension, aby dodać rozszerzenie kondycji aplikacji do definicji modelu zestawu skalowania.

# Define the scale set variables
$vmScaleSetName = "myScaleSet"
$vmScaleSetResourceGroup = "myResourceGroup"

# Define the application health extension properties
$publicConfig = @{"protocol" = "http"; "port" = 80; "requestPath" = "/healthEndpoint"; "gracePeriod" = 600};
$extensionName = "myHealthExtension"
$extensionType = "ApplicationHealthWindows"
$publisher = "Microsoft.ManagedServices"

# Get the scale set object
$vmScaleSet = Get-AzVmss `
  -ResourceGroupName $vmScaleSetResourceGroup `
  -VMScaleSetName $vmScaleSetName

# Add the application health extension to the scale set model
Add-AzVmssExtension -VirtualMachineScaleSet $vmScaleSet `
  -Name $extensionName `
  -Publisher $publisher `
  -Setting $publicConfig `
  -Type $extensionType `
  -TypeHandlerVersion "2.0" `
  -AutoUpgradeMinorVersion $True

# Update the scale set
Update-AzVmss -ResourceGroupName $vmScaleSetResourceGroup `
  -Name $vmScaleSetName `
  -VirtualMachineScaleSet $vmScaleSet
  
# Upgrade instances to install the extension.
Update-AzVmssInstance -ResourceGroupName $vmScaleSetResourceGroup `
  -VMScaleSetName $vmScaleSetName `
  -InstanceId '*'

Zastosuj rozszerzenie kondycji aplikacji przy użyciu tworzenia lub aktualizowania.

PUT `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachineScaleSets/myScaleSet/extensions/myHealthExtension?api-version=2018-10-01`

Request body
{
  "name": "myHealthExtension",
  "location": "<location>",
  "properties": {
    "publisher": "Microsoft.ManagedServices",
    "type": "ApplicationHealthWindows",
    "autoUpgradeMinorVersion": true,
    "typeHandlerVersion": "2.0",
    "settings": {
      "protocol": "<protocol>",
      "port": <port>,
      "requestPath": "</requestPath>",
      "intervalInSeconds": <intervalInSeconds>,
      "numberOfProbes": <numberOfProbes>,
      "gracePeriod": <gracePeriod>
    }
  }
}

Uaktualnij maszyny wirtualne w zestawie skalowania. Ten krok jest wymagany tylko wtedy, gdy zestaw skalowania korzysta z zasad ręcznego uaktualniania. Aby uzyskać więcej informacji na temat zasad uaktualniania, zobacz temat Upgrade policies for Virtual Machine Scale Sets (Zasady uaktualniania dla zestawów skalowania maszyn wirtualnych)

POST `/subscriptions/<subscriptionId>/resourceGroups/<myResourceGroup>/providers/Microsoft.Compute/virtualMachineScaleSets/< myScaleSet >/manualupgrade?api-version=2022-08-01`

Request body
{
  "instanceIds": ["*"]
}

#!/bin/bash

# Open firewall port (replace with your firewall rules as needed)
sudo iptables -A INPUT -p tcp --dport 8000 -j ACCEPT

# Create Python HTTP server for responding with JSON
cat <<EOF > server.py
import json
from http.server import BaseHTTPRequestHandler, HTTPServer

# Function to generate the JSON response
def generate_response_json():
    return json.dumps({
        "ApplicationHealthState": "Healthy",
        "CustomMetrics": json.dumps({
            "RollingUpgrade": {
                "PhaseOrderingNumber": 1,
                "SkipUpgrade": "false"
            }
        })
    })

class RequestHandler(BaseHTTPRequestHandler):
    def do_GET(self):
        # Respond with HTTP 200 and JSON content
        self.send_response(200)
        self.send_header('Content-type', 'application/json')
        self.end_headers()
        response = generate_response_json()
        self.wfile.write(response.encode('utf-8'))

# Set up the HTTP server
def run(server_class=HTTPServer, handler_class=RequestHandler):
    server_address = ('localhost', 8000)
    httpd = server_class(server_address, handler_class)
    print('Starting server on port 8000...')
    httpd.serve_forever()

if __name__ == "__main__":
    run()
EOF

# Run the server in the background
python3 server.py &

# Store the process ID of the server
SERVER_PID=$!

# Wait a few seconds to ensure the server starts
sleep 2

# Confirm execution
echo "Server has been started on port 8000 with PID $SERVER_PID"

# Define the script path
$scriptPath = "$env:TEMP\server.ps1"

# Create the PowerShell HTTP Server Script
$serverScript = @"
`$Hso = New-Object Net.HttpListener
`$Hso.Prefixes.Add('http://localhost:8000/')
`$Hso.Start()

Write-Host 'Starting server on port 8000...'

# Function to Generate JSON Response (Matching Python Format)
function GenerateResponseJson {
    # Create JSON string for CustomMetrics
    `$customMetricsJson = (@{
        'RollingUpgrade' = @{
            'PhaseOrderingNumber' = 1
            'SkipUpgrade' = 'false'
        }
    } | ConvertTo-Json -Depth 10) -replace "`n", "" -replace "\s{2,}", ""  # Ensuring a single-line JSON string

    # Create main JSON response
    `$response = @{
        'ApplicationHealthState' = 'Healthy'
        'CustomMetrics' = `$customMetricsJson  # Embed JSON string inside JSON
    }

    return (`$response | ConvertTo-Json -Depth 10)
}

# Keep the server running
while (`$Hso.IsListening) {
    try {
        `$context = `$Hso.GetContext()
        `$response = `$context.Response
        `$response.StatusCode = 200
        `$response.ContentType = 'application/json'
        `$responseJson = GenerateResponseJson
        `$responseBytes = [System.Text.Encoding]::UTF8.GetBytes(`$responseJson)
        `$response.OutputStream.Write(`$responseBytes, 0, `$responseBytes.Length)
        `$response.Close()
        Write-Host "Responded to request at $(Get-Date)"
    }
    catch {
        Write-Host "Error occurred: $_"
    }
}
"@

# Write the script to a file
$serverScript | Out-File -FilePath $scriptPath -Encoding UTF8

# Verify if the file exists before starting the process
if (Test-Path $scriptPath) {
    Write-Host "Server script successfully created at $scriptPath"
    Start-Process -NoNewWindow -FilePath "powershell.exe" -ArgumentList "-ExecutionPolicy Bypass -File `"$scriptPath`"" -PassThru | ForEach-Object {
        # Store Process ID
        $SERVER_PID = $_.Id
        Write-Host "Server has been started on port 8000 with PID $SERVER_PID"
    }
} else {
    Write-Host "Error: Server script not found at $scriptPath"
}

az vmss get-instance-view \
  --resource-group <resource-group-name> \
  --name <vmss-name> \
  --instance-id <instance-id>

Przykładowe dane wyjściowe (fragment kodu):

{
  "extensions": [
    {
      "name": "ApplicationHealthExtension",
      "substatuses": [
        {
          "code": "ComponentStatus/CustomMetrics/succeeded",
          "message": "{\"rollingUpgrade\": {\"PhaseOrderingNumber\": 2, \"SkipUpgrade\": false}}"
        }
      ]
    }
  ]
}

Metryki niestandardowe znajdują się w polu message substatusu ComponentStatus/CustomMetrics/succeeded.

Get-AzVmssVM `
  -ResourceGroupName <resource-group-name> `
  -VMScaleSetName <vmss-name> `
  -InstanceId <instance-id> `
  -InstanceView

Przykładowe dane wyjściowe (fragment kodu):

{
  "extensions": [
    {
      "name": "ApplicationHealthExtension",
      "substatuses": [
        {
          "code": "ComponentStatus/CustomMetrics/succeeded",
          "message": "{\"rollingUpgrade\": {\"PhaseOrderingNumber\": 2, \"SkipUpgrade\": false}}"
        }
      ]
    }
  ]
}

Metryki niestandardowe znajdują się message w polu ComponentStatus/CustomMetrics/succeeded podstatusu.

GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/virtualMachineScaleSets/{vmssName}/virtualMachines/{instanceId}/instanceView?api-version=2023-09-01

Przykładowa odpowiedź (fragment kodu):

{
  "extensions": [
    {
      "name": "ApplicationHealthExtension",
      "type": "Microsoft.ManagedServices.ApplicationHealthLinux",
      "typeHandlerVersion": "2.0",
      "substatuses": [
        {
          "code": "ComponentStatus/CustomMetrics/succeeded",
          "level": "Info",
          "displayStatus": "Provisioning succeeded",
          "message": "{\"rollingUpgrade\": {\"PhaseOrderingNumber\": 2, \"SkipUpgrade\": false}}"
        }
      ]
    }
  ]
}

Metryki niestandardowe znajdują się w polu message substatusu ComponentStatus/CustomMetrics/succeeded.

az vm get-instance-view \
  --resource-group <resource-group-name> \
  --name <vm-name>

Przykładowe dane wyjściowe (fragment kodu):

{
  "extensions": [
    {
      "name": "ApplicationHealthExtension",
      "substatuses": [
        {
          "code": "ComponentStatus/CustomMetrics/succeeded",
          "message": "{\"rollingUpgrade\": {\"PhaseOrderingNumber\": 1, \"SkipUpgrade\": false}}"
        }
      ]
    }
  ]
}

Metryki niestandardowe znajdują się w polu message podstatus ComponentStatus/CustomMetrics/succeeded.

Get-AzVM `
  -ResourceGroupName <resource-group-name> `
  -Name <vm-name> `
  -Status

Przykładowe dane wyjściowe (fragment kodu):

{
  "extensions": [
    {
      "name": "ApplicationHealthExtension",
      "substatuses": [
        {
          "code": "ComponentStatus/CustomMetrics/succeeded",
          "message": "{\"rollingUpgrade\": {\"PhaseOrderingNumber\": 1, \"SkipUpgrade\": false}}"
        }
      ]
    }
  ]
}

Metryki niestandardowe znajdują się w polu message podstanu ComponentStatus/CustomMetrics/succeeded.

GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/virtualMachines/{vmName}/instanceView?api-version=2023-09-01

Przykładowa odpowiedź (fragment kodu):

{
  "extensions": [
    {
      "name": "ApplicationHealthExtension",
      "type": "Microsoft.ManagedServices.ApplicationHealthLinux",
      "typeHandlerVersion": "2.0",
      "substatuses": [
        {
          "code": "ComponentStatus/CustomMetrics/succeeded",
          "level": "Info",
          "displayStatus": "Provisioning succeeded",
          "message": "{\"rollingUpgrade\": {\"PhaseOrderingNumber\": 1, \"SkipUpgrade\": false}}"
        }
      ]
    }
  ]
}

Metryki niestandardowe znajdują się w polu messageComponentStatus/CustomMetrics/succeeded podstatusu.