Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ERROR: Scope must be a valid resource id
See original GitHub issue
az feedbackauto-generates most of the information requested below, as of CLI version 2.0.62
Related command az monitor metrics alert create
Describe the bug When trying to create alert for Logic App failure, I am getting ERROR no matter what is actually provided as scopes
To Reproduce use following SHELL script:
ALERT_NAME="Scheduling $(LOGIC_APP_NAME) failed"
ALERT_DESCRYPTION=“$ALERT_NAME at least 3 times in last 15 minutes”
RESOURCE_ID=az resource show -n '$(LOGIC_APP_NAME)' --resource-group $(RESOURCE_GROUP) --resource-type Microsoft.Logic/workflows --query id
az monitor metrics alert create
–name “$ALERT_NAME”
–description “$ALERT_DESCRYPTION”
–resource-group $(RESOURCE_GROUP)
–scopes $RESOURCE_ID
–condition “total Runs Failed > 2”
–action $(ACTION)
–severity 4
`
Expected behavior
Additional context I am using Azure Resource Manager connection
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@witekkij Thank you for reaching out, we are looking into it.
Thank you for quick help, most probably its problem with variable. I ended up using following string interpolation –scopes “/subscriptions/$(SUBSCRYPTION_ID)/resourceGroups/$(RESOURCE_GROUP)/providers/Microsoft.Logic/workflows/$(LOGIC_APP_NAME)” \