alertsmanagement RP 2019-05-05-preview enum is not consistent with the service actually supported

[njuCZ]

this is a snippet in the swagger file specification/alertsmanagement/resource-manager/Microsoft.AlertsManagement/preview/2019-05-05-preview/AlertsManagement.json:

"monitorService": {
          "type": "string",
          "description": "Monitor service on which the rule(monitor) is set.",
          "readOnly": true,
          "enum": [
            "Application Insights",
            "ActivityLog Administrative",
            "ActivityLog Security",
            "ActivityLog Recommendation",
            "ActivityLog Policy",
            "ActivityLog Autoscale",
            "Log Analytics",
            "Nagios",
            "Platform",
            "SCOM",
            "ServiceHealth",
            "SmartDetector",
            "VM Insights",
            "Zabbix"
          ],
          "x-ms-enum": {
            "name": "MonitorService",
            "modelAsString": true
          }
},

However this is the error msg from the backend service:

Invalid input parameters: The given monitor service Nagios is not supported as a filter. The supported monitor services are: ActivityLog Administrative,ActivityLog Autoscale,ActivityLog Policy,ActivityLog Recommendation,ActivityLog Security,Application Insights,Azure Backup,Data Box Edge,Data Box Gateway,Health Platform,Log Analytics,Platform,Resource Health.

the values of enum defined in the swagger is not consistent with the actual supported enum values

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @AzmonAlerts.

[ofirmanor]

quick update - this inconsistency will be fixed in the next API version of action rule, internal tracking id 7484381 Thanks!