-
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
BUG fix: Fixing type of MetricValue.Count to be double instead of the incorrect int64 it had before #6485
Conversation
… Adding documentation to reduce number of warnings in validation.
…breaking change
…t int64 it had before
SDK Automation [Logs] (Generated from 5251be8)Python: Azure/azure-sdk-for-python
Java: Azure/azure-sdk-for-java
Go: Azure/azure-sdk-for-go
JavaScript: Azure/azure-sdk-for-js
Ruby: Azure/azure-sdk-for-ruby
|
Automation for azure-sdk-for-rubyA PR has been created for you: |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Can one of the admins verify this patch? |
Addresses issue #5130 |
Issue #2371 has been addressed before. It is no longer a valid issue, since the Metrics_list argument is already declared as an integer. |
Issue #2513 has already been addressed too: the names of top and orderby no longer reference the $ sign they used to reference. |
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", |
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.
It seems like "count" should be a whole number. Can you get a count of 1.5?
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.
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.
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.
OK, you might consider changing the name in the future then, since a count shouldn't be able to be a double AFAIK
… and it requires at least a start time.
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>
Can I, please, have this PR merged? |
… 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.
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:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.