# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Microsoft Azure Microsoft.Logz VM Host API
  version: 1.0.0
extends: openapi/microsoft-azure-vm-host-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 6
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logz/monitors/{monitorName}/accounts/{subAccountName}/vmHostPayload'].post
  update:
    x-apievangelist-phrasing:
      intent: Get the Logz.io agent install payload for a sub account
      effect: read
      questions:
      - What payload do I need to install the Logz.io agent on a VM for a sub account?
      - Where do I get the agent install details tied to a Logz sub account?
      instructions:
      - text: Get the VM agent install payload for sub account {subAccountName} on monitor {monitorName}.
        slots:
          subAccountName: path.subAccountName
          monitorName: path.monitorName
      - text: Fetch the Logz.io agent payload for sub account {subAccountName}.
        slots:
          subAccountName: path.subAccountName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logz/monitors/{monitorName}/accounts/{subAccountName}/vmHostUpdate'].post
  update:
    x-apievangelist-phrasing:
      intent: Update VM collection for a Logz sub account
      effect: write
      questions:
      - How do I tell a Logz sub account that the agent is now installed on certain VMs?
      - Can I mark VMs as installed or removed in a sub account's collection?
      instructions:
      - text: Update the VM collection for sub account {subAccountName} on monitor {monitorName} with VMs {vmResourceIds}.
        slots:
          subAccountName: path.subAccountName
          monitorName: path.monitorName
          vmResourceIds: requestBody.vmResourceIds
      - text: Set VMs {vmResourceIds} to state {state} for sub account {subAccountName}.
        slots:
          vmResourceIds: requestBody.vmResourceIds
          state: requestBody.state
          subAccountName: path.subAccountName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logz/monitors/{monitorName}/accounts/{subAccountName}/listVMHosts'].post
  update:
    x-apievangelist-phrasing:
      intent: List VMs monitored by a Logz sub account
      effect: read
      questions:
      - Which compute resources is my Logz sub account currently monitoring?
      - What VMs send logs through a particular sub account?
      instructions:
      - text: List VM hosts monitored by sub account {subAccountName} on monitor {monitorName}.
        slots:
          subAccountName: path.subAccountName
          monitorName: path.monitorName
      - text: Show the machines under sub account {subAccountName}.
        slots:
          subAccountName: path.subAccountName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logz/monitors/{monitorName}/vmHostPayload'].post
  update:
    x-apievangelist-phrasing:
      intent: Get the Logz.io agent install payload for a monitor
      effect: read
      questions:
      - What request body do I pass to install the Logz.io agent on a VM for my main monitor?
      - How do I get the agent install payload at the main account level?
      instructions:
      - text: Get the VM agent install payload for monitor {monitorName}.
        slots:
          monitorName: path.monitorName
      - text: Fetch the main-account Logz.io agent payload for {monitorName}.
        slots:
          monitorName: path.monitorName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logz/monitors/{monitorName}/vmHostUpdate'].post
  update:
    x-apievangelist-phrasing:
      intent: Update VM collection for a Logz main monitor
      effect: write
      questions:
      - How do I update the main Logz monitor after installing the agent on VMs?
      - Can I record VM agent installs at the main account level rather than a sub account?
      instructions:
      - text: Update the VM collection on monitor {monitorName} with VMs {vmResourceIds}.
        slots:
          monitorName: path.monitorName
          vmResourceIds: requestBody.vmResourceIds
      - text: Mark VMs {vmResourceIds} as {state} on main monitor {monitorName}.
        slots:
          vmResourceIds: requestBody.vmResourceIds
          state: requestBody.state
          monitorName: path.monitorName
      method: generated
      generated: '2026-09-26'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Logz/monitors/{monitorName}/listVMHosts'].post
  update:
    x-apievangelist-phrasing:
      intent: List VMs monitored by a Logz main account
      effect: read
      questions:
      - Which compute resources is my main Logz monitor watching?
      - What VMs are being monitored at the main account level?
      instructions:
      - text: List VM hosts monitored by monitor {monitorName}.
        slots:
          monitorName: path.monitorName
      - text: Show the machines watched by main monitor {monitorName}.
        slots:
          monitorName: path.monitorName
      method: generated
      generated: '2026-09-26'