Azure / Azure/azure-quickstart-templates
azure-quickstart-templates/101-backup-oms-monitoring/ Issue
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------
Sorry to hear you had a bad experience with one of the templates :worried: But, in case you're just asking a question, we're happy to help. You can also check if the question might already have been asked here https://github.com/Azure/azure-quickstart-templates/issues?utf8=%E2%9C%93&q=is%3Aissue
We've created an outline of recommended sections to fill out that will help make this Pull Request awesome!
--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------
[Template Name goes here](Template link goes here)
### Issue Details
Getting below error when open Solution from log Analytics
An error has occurred
{"error":{"message":"The request had some invalid properties","code":"BadArgumentError","innererror":{"code":"SyntaxError","message":"Syntax Error","information":{"details":"{\"error\":{\"code\":\"Bad request\",\"message\":\"Request is invalid and cannot be executed.\",\"innererror\":{\"code\":\"SEM0100\",\"message\":\"'project' operator: Failed to resolve scalar expression named 'AlertSeverity_s'\",\"@context\":{\"activityId\":\"f286c650-7cd6-455a-a706-287bd4cdb5e2\"},\"@errorCode\":\"SEM0100\",\"@errorMessage\":\"'project' operator: Failed to resolve scalar expression named 'AlertSeverity_s'\"}}}"}}}}
See less
a few seconds ago
### Repro steps (*if necessary, delete otherwise*)
1. Log Analytic --> Click on Workspace
2. Settings --> Solutions --> Azure Backup
3. Click on Azure Backup Monitoring Solution-- After Sometime Error will Come Notification Windows
4.
5.

Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the issue from the azure-quickstart-templates/101-backup-oms-monitoring/ template: open the Azure Backup Monitoring Solution through Log Analytics and capture the failing query. Trace the query error mentioning the missing AlertSeverity_s expression, and consider the issue done when the solution opens without that BadArgumentError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100