[Azure Storage Account] Add default_timegrain configuration option - #15501
Merged
Conversation
zmoog
added
Integration:azure_metrics
Contributor
🚀 Benchmarks reportTo see the full report comment with |
zmoog
marked this pull request as ready for review
October 6, 2025 09:21
# Conflicts: # packages/azure_metrics/changelog.yml # packages/azure_metrics/manifest.yml
zmoog
force-pushed
the
zmoog/feat/azure/storage/default-timegrain
branch
from
October 6, 2025 09:30
3f183f0 to
29574ea
Compare
Contributor
Author
|
I will run a final test when 8.18.8, 8.19.5, 9.0.8, and 9.1.5 will be available. |
MichaelKatsoulis
approved these changes
Oct 6, 2025
💚 Build Succeeded
History
cc @zmoog |
andrewkroh
added
the
documentation
joecompute
approved these changes
Oct 6, 2025
Contributor
Author
|
Quick test on 8.18.8 with PT1M/300s: 
I could collect PT1M metrics: 
|
Contributor
|
Package azure_metrics - 1.11.0 containing this change is available at https://epr.elastic.co/package/azure_metrics/1.11.0/ |
agithomas
pushed a commit
to agithomas/integrations
that referenced
this pull request
Oct 30, 2025
…lastic#15501) Adds a new "Default Timegrain" configuration option to allow users to customize the timegrain used in the Storage Account integration. 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#15464.
tehbooom
pushed a commit
to tehbooom/integrations
that referenced
this pull request
Nov 19, 2025
…lastic#15501) Adds a new "Default Timegrain" configuration option to allow users to customize the timegrain used in the Storage Account integration. 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#15464.
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
5 participants
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 Timegrain" configuration option to allow users to customize the timegrain used in the Storage Account integration. 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 #15464.
Checklist
changelog.ymlfile.I have verified that any added dashboard complies with Kibana's Dashboard good practicesRelated issues
Screenshots