API Evangelist conversational phrasing for Microsoft Azure Metrics Advisor Anomaly Detection API

# 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 Metrics Advisor Anomaly Detection API
  version: 1.0.0
extends: openapi/microsoft-azure-anomaly-detection-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 11
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get an anomaly detection configuration
      effect: read
      questions:
      - What detection settings does one of my anomaly detection configurations use?
      - Can I look up a single detection configuration by its ID in Metrics Advisor?
      instructions:
      - text: Get anomaly detection configuration {configurationId}.
        slots:
          configurationId: path.configurationId
      - text: Show the thresholds set in detection config {configurationId}.
        slots:
          configurationId: path.configurationId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete an anomaly detection configuration
      effect: destructive
      questions:
      - How do I remove a detection configuration I no longer use?
      - Can I delete a metric's anomaly detection setup?
      instructions:
      - text: Delete anomaly detection configuration {configurationId}.
        slots:
          configurationId: path.configurationId
      - text: Remove detection config {configurationId} permanently.
        slots:
          configurationId: path.configurationId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}'].patch
  update:
    x-apievangelist-phrasing:
      intent: Update an anomaly detection configuration
      effect: write
      questions:
      - Can I tune the sensitivity on an existing detection configuration?
      - How do I add a per-series override to a detection config I already have?
      instructions:
      - text: Rename anomaly detection configuration {configurationId} to {name}.
        slots:
          configurationId: path.configurationId
          name: requestBody.name
      - text: Change the whole-metric settings of existing config {configurationId} to {wholeMetricConfiguration}.
        slots:
          configurationId: path.configurationId
          wholeMetricConfiguration: requestBody.wholeMetricConfiguration
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations'].post
  update:
    x-apievangelist-phrasing:
      intent: Create an anomaly detection configuration
      effect: write
      questions:
      - How do I set up anomaly detection on a new metric?
      - Can I override detection settings for specific dimension groups when I create a configuration?
      instructions:
      - text: Create an anomaly detection configuration {name} for metric {metricId}.
        slots:
          name: requestBody.name
          metricId: requestBody.metricId
      - text: Create detection config {name} on metric {metricId} with whole-metric settings {wholeMetricConfiguration}.
        slots:
          name: requestBody.name
          metricId: requestBody.metricId
          wholeMetricConfiguration: requestBody.wholeMetricConfiguration
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}/alert/anomaly/configurations'].get
  update:
    x-apievangelist-phrasing:
      intent: List alert configurations tied to a detection config
      effect: read
      questions:
      - Which alerting configurations fire from this anomaly detection configuration?
      - Who gets alerted when a detection config finds anomalies?
      instructions:
      - text: List the anomaly alerting configurations for detection config {configurationId}.
        slots:
          configurationId: path.configurationId
      - text: Show {maxpagesize} alert configs linked to detection config {configurationId}.
        slots:
          maxpagesize: query.$maxpagesize
          configurationId: path.configurationId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}/series/query'].post
  update:
    x-apievangelist-phrasing:
      intent: Query series data enriched by anomaly detection
      effect: read
      questions:
      - Can I see a metric series with its expected values and boundaries over a time range?
      - What did the detector predict for specific series between two dates?
      instructions:
      - text: Get enriched series {series} from detection config {configurationId} between {startTime} and {endTime}.
        slots:
          series: requestBody.series
          configurationId: path.configurationId
          startTime: requestBody.startTime
          endTime: requestBody.endTime
      - text: Show expected values and bounds for series {series} under config {configurationId}.
        slots:
          series: requestBody.series
          configurationId: path.configurationId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}/anomalies/query'].post
  update:
    x-apievangelist-phrasing:
      intent: Query anomalies found by a detection configuration
      effect: read
      questions:
      - What anomalies were detected last week under this configuration?
      - Can I filter detected anomalies by severity or dimension?
      instructions:
      - text: List anomalies detected by config {configurationId} from {startTime} to {endTime}.
        slots:
          configurationId: path.configurationId
          startTime: requestBody.startTime
          endTime: requestBody.endTime
      - text: Find anomalies under config {configurationId} between {startTime} and {endTime} matching {filter}.
        slots:
          configurationId: path.configurationId
          startTime: requestBody.startTime
          endTime: requestBody.endTime
          filter: requestBody.filter
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}/anomalies/dimension/query'].post
  update:
    x-apievangelist-phrasing:
      intent: List dimension values that had anomalies
      effect: read
      questions:
      - Which regions or products had anomalies in a given period?
      - What values of one dimension show up among detected anomalies?
      instructions:
      - text: List values of dimension {dimensionName} with anomalies under config {configurationId} from {startTime} to {endTime}.
        slots:
          dimensionName: requestBody.dimensionName
          configurationId: path.configurationId
          startTime: requestBody.startTime
          endTime: requestBody.endTime
      - text: Which {dimensionName} values were anomalous for config {configurationId}.
        slots:
          dimensionName: requestBody.dimensionName
          configurationId: path.configurationId
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}/incidents/query'].get
  update:
    x-apievangelist-phrasing:
      intent: Fetch the next page of anomaly incidents
      effect: read
      questions:
      - How do I get the next page of incidents using a continuation token?
      - Can I keep paging incident results after my first incident query?
      instructions:
      - text: Get the next page of incidents for detection config {configurationId} using token {token}.
        slots:
          configurationId: path.configurationId
          token: query.$token
      - text: Continue the incident listing for config {configurationId} with page size {maxpagesize}.
        slots:
          configurationId: path.configurationId
          maxpagesize: query.$maxpagesize
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}/incidents/query'].post
  update:
    x-apievangelist-phrasing:
      intent: Query incidents under a detection configuration
      effect: read
      questions:
      - What incidents did my detection configuration raise in a time window?
      - Can I narrow incident results with a filter on the first query?
      instructions:
      - text: Find incidents under detection config {configurationId} from {startTime} to {endTime}.
        slots:
          configurationId: path.configurationId
          startTime: requestBody.startTime
          endTime: requestBody.endTime
      - text: Search incidents for config {configurationId} between {startTime} and {endTime} matching {filter}.
        slots:
          configurationId: path.configurationId
          startTime: requestBody.startTime
          endTime: requestBody.endTime
          filter: requestBody.filter
      method: generated
      generated: '2026-10-01'
- target: $.paths['/enrichment/anomalyDetection/configurations/{configurationId}/incidents/{incidentId}/rootCause'].get
  update:
    x-apievangelist-phrasing:
      intent: Get the root cause of an anomaly incident
      effect: read
      questions:
      - What caused this anomaly incident?
      - Which dimension contributed most to an incident?
      instructions:
      - text: Get the root cause of incident {incidentId} under detection config {configurationId}.
        slots:
          incidentId: path.incidentId
          configurationId: path.configurationId
      - text: Explain what drove incident {incidentId} for config {configurationId}.
        slots:
          incidentId: path.incidentId
          configurationId: path.configurationId
      method: generated
      generated: '2026-10-01'