-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Monitoring] Add metric alerts api 2018-03-01 #2620
Conversation
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-libraries-for-javaThe initial PR has been merged into your service PR: |
@LeoVannelli this went through the API review board now, correct? 🙂 |
@ravbhatnagar new API |
@rboucher. Please notify me when this PR is accepted. Docs are waiting on it. |
@ravbhatnagar Can you review this? This is the GA version of metricalerts API. Preview version was already reviewed by you. @LeoVannelli added information above about the deltas. |
@AutorestCI rebuild azure-sdk-for-python |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one comment. Other than that looks good.
"evaluationFrequency": "PT1M", | ||
"windowSize": "PT15M", | ||
"criteria": { | ||
"odata.type": "Microsoft.Azure.Monitor.SingleResourceMultipleMetricCriteria", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we make odata.type as an enum and then set modelAsString to true?
Signing off from ARM side. Feel free to merge based on the response to above comment. |
@AutorestCI regenerate azure-sdk-for-python |
@LeoVannelli thanks for your response regarding API review board. You mentioned the preview version got "stuck" in review - but what about this version? Has it been reviewed by the board or what is the plan? 🙂 |
Pull request has been updated with review feedback. Review board has approved. Waiting on final review and merge. |
@olydis Leo had a review and it was signed off in the meeting. Can we get this merged? We are waiting on this merge to go through for us update the docs. Regards, |
"get": { | ||
"tags": [ "MetricAlertsStatus" ], | ||
"description": "Retrieve an alert rule status.", | ||
"operationId": "MetricAlertsStatus_listByName", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"operationId": "MetricAlertsStatus_listByName",
Should be
"operationId": "MetricAlertsStatus_ListByName",
}, | ||
"criteria": { | ||
"$ref": "#/definitions/MetricAlertCriteria", | ||
"description": "criteria" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "criteria"
is really vague and it causes a validation error -- can you put in a better description?
You have a couple of small typos (mentioned in comments) and your example data isn't passing validation (see: https://travis-ci.org/Azure/azure-rest-api-specs/jobs/356119129#L733 ) |
Updated examples with corrections, not sure if all items are fixed, how can I run the test you executed to validate locally |
Hey @LeoVannelli You can run the tests locally by installing autorest and then running: # start where your readme.md file is.
cd azure-rest-api-specs/specification/monitor/resource-manager
# run the linter rules validation
autorest --azure-validator readme.md
# install the oav tool (example validation)
npm install -g oav
# run the oav tool
oav validate-example microsoft.insights/stable/2018-03-01/metricAlert_API.json
|
}, | ||
"criteria": { | ||
"$ref": "#/definitions/MetricAlertCriteria", | ||
"description": "definies the specific alert criteria information." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*defines
Any updates on this? Examples have been fixed just waiting on approval and merge. |
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-version
in the path should match theapi-version
in the spec).Quality of Swagger