Skip to content
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

BUG fix: Fixing type of MetricValue.Count to be double instead of the incorrect int64 it had before #6485

Merged
merged 31 commits into from
Jul 8, 2019

Conversation

gucalder
Copy link
Contributor

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

… Adding documentation to reduce number of warnings in validation.
@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 27, 2019

SDK Automation [Logs] (Generated from 5251be8)

Pending Python: Azure/azure-sdk-for-python
  • Package generation pending.
Pending Java: Azure/azure-sdk-for-java
  • Package generation pending.
Pending Go: Azure/azure-sdk-for-go
  • Package generation pending.
Pending JavaScript: Azure/azure-sdk-for-js
  • Package generation pending.
Pending Ruby: Azure/azure-sdk-for-ruby
  • Package generation pending.

@AutorestCI
Copy link

AutorestCI commented Jun 27, 2019

Automation for azure-sdk-for-ruby

A PR has been created for you:
Azure/azure-sdk-for-ruby#2695

@AutorestCI
Copy link

AutorestCI commented Jun 27, 2019

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#6107

@AutorestCI
Copy link

AutorestCI commented Jun 27, 2019

Automation for azure-sdk-for-java

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-java#2993

@AutorestCI
Copy link

AutorestCI commented Jun 27, 2019

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#5206

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@gucalder
Copy link
Contributor Author

Addresses issue #5130

@gucalder
Copy link
Contributor Author

Issue #2371 has been addressed before. It is no longer a valid issue, since the Metrics_list argument is already declared as an integer.

@gucalder
Copy link
Contributor Author

Issue #2513 has already been addressed too: the names of top and orderby no longer reference the $ sign they used to reference.

@gucalder
Copy link
Contributor Author

Issue #2575 has been addressed too: the name of the query parameter "metric" changed to "metricnames" as required.

"type": "integer",
"format": "int64",
"type": "number",
"format": "double",
Copy link
Contributor

@nschonni nschonni Jun 28, 2019

Choose a reason for hiding this comment

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

It seems like "count" should be a whole number. Can you get a count of 1.5?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeap, we discuss whether to change it in the backend (and leave this spec as it was) or change it in the spec. The reason for it to be a double (NOTE: we do not generate the metric, we just pass it on) is uncertain, but it might have something to do with the fact that this could actually be the average of several counts.

We thought that it after that, we decided to change the spec to reflect the current response of the backend to minimize customer impact.

Copy link
Contributor

Choose a reason for hiding this comment

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

OK, you might consider changing the name in the future then, since a count shouldn't be able to be a double AFAIK

@gucalder
Copy link
Contributor Author

gucalder commented Jun 28, 2019

The latest change is a bug in the spec (#2467.) The $filter is actually not optional in the ActivityLogs API and it requires at least the start date/time. So I removed two examples that were missing the $filter.

# Conflicts:
#	specification/monitor/resource-manager/Microsoft.Insights/stable/2015-04-01/activityLogs_API.json
#	specification/monitor/resource-manager/Microsoft.Insights/stable/2015-04-01/examples/GetActivityLogsNoParams.json
#	specification/monitor/resource-manager/Microsoft.Insights/stable/2015-04-01/examples/GetActivityLogsSelected.json

Signed-off-by: Guillermo Calderón_Meza <gucalder@microsoft.com>
@gucalder
Copy link
Contributor Author

gucalder commented Jul 3, 2019

Can I, please, have this PR merged?

@lmazuel lmazuel merged commit ca0869b into Azure:master Jul 8, 2019
celikcigdem pushed a commit to celikcigdem/azure-rest-api-specs that referenced this pull request Jul 17, 2019
… incorrect int64 it had before (Azure#6485)

* [Monitor] Make all attributes of EventData class readonly (Azure#2254)

* [Monitor] Fixing issue with metricnamespace specification as client level argument Azure#2565

* [Monitor] Fixing incorrect specification of top parameter for Metrics API (Azure#2655)

* Add two missing "by subscription" operations.

* Remove "examples" nodes as requested since they are not used anymore. Adding documentation to reduce number of warnings in validation.

* Add the serviceBusRuleId back into the DiagnosticSetting resource spec.

* Fix some issues with the examples

* [Monitor] Fix issue Azure#3585: revert previous commit since it is a breaking change

* Add unit "BitsPerSecond" to the metrics specs.

* Fixing workspace Id documentation

* Add the Log Analytics destination type flag to the Diagnostic Settings objects

* Fix a typo in a description

* Fixing type of MetricValue.Count to be double instead of the incorrect int64 it had before

* Fixing issue Azure#2467 In List Activity Logs $filter is not optional and it requires at least a start time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants