[Monitor] Adding new multi-dimensional metrics API#1620
[Monitor] Adding new multi-dimensional metrics API#1620sergey-shandar merged 14 commits intoAzure:currentfrom
Conversation
…ng issue Azure#1475: incorrect example in LogProfiles API documentation for CreateOrUpdate, fixing incorrect logProfiles example names.
…ivityLogAlerts API.
|
First part of the, now closed, PR #1614. This part includes only changes to data-plane. |
|
@jianghaolu this is Data plane btw, so ARM guidelines and RPC linter rules are not enforced here. The focus should be more on SDK and good practices that you would recommend |
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues Send feedback and make AutoRest Linter Azure Bot smarter day by day! Thanks for your co-operation. |
|
@salameer @sergey-shandar was kind enough to take over - but I agree with what you said :) |
|
@gucalder I'll publish my review tomorrow. |
… into currentAltMetrics
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues Send feedback and make AutoRest Linter Azure Bot smarter day by day! Thanks for your co-operation. |
|
No modification for AutorestCI/azure-sdk-for-ruby |
|
No modification for AutorestCI/azure-sdk-for-node |
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-versionin the path should match theapi-versionin the spec).Quality of Swagger