No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Here's the Azure API on which the Pulumi API is based. The workspaceName field is not optional, apparently.

image.png

<@U012UJTT55M> thanks for the impromptu reply :smile:  !
However, I kept on having this issue, have been searching around but still couldn't resolve this.

`error: autorest/azure: Service returned an error. Status=404 Code="NotFound" Message="{\"error\":{\"code\":\"NotFound\",\"message\":\"Couldn't find workspaceMetadata of workspace id a30b9da9-9fcb-4c38-8259-ec7001823d12\"`

<https://docs.microsoft.com/en-us/rest/api/securityinsights/stable/alert-rules/create-or-update>

Heh.. I forgot to include the link earlier :slightly_smiling_face:

I'm afraid I don't know anything about Azure and workspace metadata. Have you pinged the <#CRVK66N5U|> channel?

I were able to create the scheduled-query rules without needing a workspace which can be seen here <https://docs.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-log>

Why does the Pulumi API require it ?

`az monitor scheduled-query create -g {ResourceGroup} -n {nameofthealert} --scopes {vm_id} --condition "count \'union Event, Syslog | where TimeGenerated &gt; ago(1h) | where EventLevelName == \"Error\" or SeverityLevel== \"err\"\' &gt; 2" --description {descriptionofthealert}`