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

[Monitor] In List Activity Logs $filter is not optional and it requires at least a start time. #2467

Open
gucalder opened this issue Feb 9, 2018 · 1 comment
Assignees
Labels
Monitor - ActivityLogs Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@gucalder
Copy link
Contributor

gucalder commented Feb 9, 2018

In List Activity Logs $filter is not optional and it requires at least a start time.
Fix the example that says no $filter / $select, it is not correct.
Fix the documentation of $filter.

This looks like a breaking change, but the call fails without $filter, so this is making it work instead of breaking it.

@olydis olydis added the Monitor Monitor, Monitor Ingestion, Monitor Query label Feb 21, 2018
@olydis olydis assigned gucalder and unassigned olydis Feb 21, 2018
@bsiegel bsiegel added the Service Attention Workflow: This issue is responsible by Azure service team. label Sep 26, 2018
@asheniam
Copy link

Thanks for reporting this. We will fix the example in the doc.

@kshitizm kshitizm removed the Monitor Monitor, Monitor Ingestion, Monitor Query label Jun 27, 2019
gucalder added a commit to gucalder/azure-rest-api-specs that referenced this issue Jun 28, 2019
lmazuel pushed a commit that referenced this issue Jul 8, 2019
… incorrect int64 it had before (#6485)

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

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

* [Monitor] Fixing incorrect specification of top parameter for Metrics API (#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 #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 #2467 In List Activity Logs $filter is not optional and it requires at least a start time.
celikcigdem pushed a commit to celikcigdem/azure-rest-api-specs that referenced this issue 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
Monitor - ActivityLogs Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

6 participants