Skip to content

[Monitor] Adding new multi-dimensional metrics API#1620

Merged
sergey-shandar merged 14 commits intoAzure:currentfrom
AuxMon:currentAltMetrics
Sep 1, 2017
Merged

[Monitor] Adding new multi-dimensional metrics API#1620
sergey-shandar merged 14 commits intoAzure:currentfrom
AuxMon:currentAltMetrics

Conversation

@gucalder
Copy link
Copy Markdown
Contributor

@gucalder gucalder commented Aug 31, 2017

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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@gucalder
Copy link
Copy Markdown
Contributor Author

First part of the, now closed, PR #1614. This part includes only changes to data-plane.

@salameer
Copy link
Copy Markdown
Member

@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

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/monitor/data-plane/readme.md
Before the PR: Warning(s): 1 Error(s): 3
After the PR: Warning(s): 1 Error(s): 3

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

@jianghaolu
Copy link
Copy Markdown
Contributor

@salameer @sergey-shandar was kind enough to take over - but I agree with what you said :)

@sergey-shandar
Copy link
Copy Markdown
Contributor

@gucalder I'll publish my review tomorrow.

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/monitor/data-plane/readme.md
Before the PR: Warning(s): 1 Error(s): 3
After the PR: Warning(s): 1 Error(s): 3

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

Copy link
Copy Markdown
Contributor

@sergey-shandar sergey-shandar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AutorestCI
Copy link
Copy Markdown

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-ruby

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-node

@gucalder gucalder deleted the currentAltMetrics branch September 12, 2017 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants