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

[v9.5.x] AzureMonitor: Fix logs query multi-resource and timespan values #67932

Merged
merged 1 commit into from
May 5, 2023

Conversation

grafanabot
Copy link
Contributor

Backport 9d16718 from #67914

* Update TimeGrain interface methods

- Make them util functions because it's simpler

* Update logs ds to appropiately set resources and timespan

* Set timespan using RCF times

* Update tests

(cherry picked from commit 9d16718)
@grafanabot grafanabot requested a review from aangelisc May 5, 2023 15:49
@grafanabot grafanabot added backport A backport PR no-changelog Skip including change in changelog/release notes type/bug area/backend datasource/Azure Azure Monitor Datasource labels May 5, 2023
@aangelisc aangelisc added this to the 9.5.x milestone May 5, 2023
@aangelisc aangelisc enabled auto-merge (squash) May 5, 2023 15:52
@github-actions
Copy link
Contributor

github-actions bot commented May 5, 2023

Backend code coverage report for PR #67932

Plugin Main PR Difference
azuremonitor 70.7% 70.6% -.1%

@github-actions
Copy link
Contributor

github-actions bot commented May 5, 2023

Frontend code coverage report for PR #67932
No changes

@aangelisc aangelisc merged commit 0c0a5ed into v9.5.x May 5, 2023
@aangelisc aangelisc deleted the backport-67914-to-v9.5.x branch May 5, 2023 16:04
@zerok zerok added add to changelog and removed no-changelog Skip including change in changelog/release notes labels Jun 29, 2023
@zerok zerok modified the milestones: 9.5.x, 9.5.6 Jun 30, 2023
@zerok zerok modified the milestones: 9.5.6, 9.5.x, 9.5.7 Jul 17, 2023
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.

3 participants