[Azure Monitor] Add default timegrain to Azure Storage Account metricset#46786
Merged
[Azure Monitor] Add default timegrain to Azure Storage Account metricset#46786
Conversation
Allows user to pick a different time grain as default. Continue using the current PT5M time grain values.
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Contributor
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Contributor
|
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services) |
Contributor
🔍 Preview links for changed docs |
Contributor
Author
|
@elastic/ingest-docs, could you review this PR when you get a chance? I'm hoping to include this change in today's FF 🙇 |
theletterf
approved these changes
Sep 30, 2025
Contributor
|
@Mergifyio backport 8.18 8.19 9.0 9.1 |
Contributor
✅ Backports have been createdDetails
|
mergify bot
pushed a commit
that referenced
this pull request
Sep 30, 2025
…set (#46786) Adds a new `default_timegrain` configuration option to allow users to customize the timegrain used in the Storage Account metricset. The default value remains PT5M, but users can now choose a different value. Without this option, users can only collect metrics with a PT5M time grain. It is a sensible default, but some users want to collect metrics with a PT1M time grain. To learn more, see elastic/integrations#15464. (cherry picked from commit 8f145b9) # Conflicts: # docs/reference/metricbeat/metricbeat-metricset-azure-storage.md # x-pack/metricbeat/module/azure/storage/_meta/docs.md
mergify bot
pushed a commit
that referenced
this pull request
Sep 30, 2025
…set (#46786) Adds a new `default_timegrain` configuration option to allow users to customize the timegrain used in the Storage Account metricset. The default value remains PT5M, but users can now choose a different value. Without this option, users can only collect metrics with a PT5M time grain. It is a sensible default, but some users want to collect metrics with a PT1M time grain. To learn more, see elastic/integrations#15464. (cherry picked from commit 8f145b9)
mergify bot
pushed a commit
that referenced
this pull request
Sep 30, 2025
…set (#46786) Adds a new `default_timegrain` configuration option to allow users to customize the timegrain used in the Storage Account metricset. The default value remains PT5M, but users can now choose a different value. Without this option, users can only collect metrics with a PT5M time grain. It is a sensible default, but some users want to collect metrics with a PT1M time grain. To learn more, see elastic/integrations#15464. (cherry picked from commit 8f145b9) # Conflicts: # docs/reference/metricbeat/metricbeat-metricset-azure-storage.md # x-pack/metricbeat/module/azure/storage/_meta/docs.md
This was referenced Sep 30, 2025
mergify bot
pushed a commit
that referenced
this pull request
Sep 30, 2025
…set (#46786) Adds a new `default_timegrain` configuration option to allow users to customize the timegrain used in the Storage Account metricset. The default value remains PT5M, but users can now choose a different value. Without this option, users can only collect metrics with a PT5M time grain. It is a sensible default, but some users want to collect metrics with a PT1M time grain. To learn more, see elastic/integrations#15464. (cherry picked from commit 8f145b9)
6 tasks
zmoog
added a commit
that referenced
this pull request
Sep 30, 2025
…set (#46786) (#46853) Adds a new `default_timegrain` configuration option to allow users to customize the timegrain used in the Storage Account metricset. The default value remains PT5M, but users can now choose a different value. Without this option, users can only collect metrics with a PT5M time grain. It is a sensible default, but some users want to collect metrics with a PT1M time grain. To learn more, see elastic/integrations#15464. (cherry picked from commit 8f145b9) # Conflicts: # docs/reference/metricbeat/metricbeat-metricset-azure-storage.md # x-pack/metricbeat/module/azure/storage/_meta/docs.md Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>
zmoog
added a commit
that referenced
this pull request
Sep 30, 2025
…set (#46786) (#46851) Adds a new `default_timegrain` configuration option to allow users to customize the timegrain used in the Storage Account metricset. The default value remains PT5M, but users can now choose a different value. Without this option, users can only collect metrics with a PT5M time grain. It is a sensible default, but some users want to collect metrics with a PT1M time grain. To learn more, see elastic/integrations#15464. (cherry picked from commit 8f145b9) # Conflicts: # docs/reference/metricbeat/metricbeat-metricset-azure-storage.md # x-pack/metricbeat/module/azure/storage/_meta/docs.md Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>
zmoog
added a commit
that referenced
this pull request
Sep 30, 2025
…set (#46786) (#46852) Adds a new `default_timegrain` configuration option to allow users to customize the timegrain used in the Storage Account metricset. The default value remains PT5M, but users can now choose a different value. Without this option, users can only collect metrics with a PT5M time grain. It is a sensible default, but some users want to collect metrics with a PT1M time grain. To learn more, see elastic/integrations#15464. (cherry picked from commit 8f145b9) Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>
zmoog
added a commit
that referenced
this pull request
Sep 30, 2025
…set (#46786) (#46854) Adds a new `default_timegrain` configuration option to allow users to customize the timegrain used in the Storage Account metricset. The default value remains PT5M, but users can now choose a different value. Without this option, users can only collect metrics with a PT5M time grain. It is a sensible default, but some users want to collect metrics with a PT1M time grain. To learn more, see elastic/integrations#15464. (cherry picked from commit 8f145b9) Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Adds a new
default_timegrainconfiguration option to allow users to customize the timegrain used in the Storage Account metricset. The default value remains PT5M, but users can now choose a different value.Without this option, users can only collect metrics with a PT5M time grain. It is a sensible default, but some users want to collect metrics with a PT1M time grain.
To learn more, see elastic/integrations#15464.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
Here are a couple of Metricbeat config to run the tests:
If you have tens of storage accounts (or more), we recommend setting
enable_batch_api: true.Related issues