Repository navigation
[Azure][container_registry] Metrics with PT1H time grain problems #7646
Description
Problem 1.
Metrics with PT1H time grain are scraped/stored every 5 minutes with 1 hour of delay:
Problem 2.
For metrics with PT1H time grain after 1h of running the integration, documents are ingested with the same timestamp, but an hour later.
tested and reproduced on stack 8.9.1:
For example: notice Sep 1, 2023 @ 14:15:00.000 - there are 2 documents with the same timestamp (for the same azure.resource.name), but those 2 documents have different ingest time - that is 1 hour apart, one with Sep 1, 2023 @ 15:15:34.000 and another with Sep 1, 2023 @ 16:15:30.000.
Note that this behavior occurs only after > 1h of running this integration
cc @zmoog
Activity
tdancheva commentedon Oct 12, 2023
A quick update on this one. Problem 2 is the same as in #7621, the fix is explained in elastic/beats#36778. @zmoog is working on a larger fix for grouping friendly with TSDB, which will work for a larger time grain than period.
botelastic commentedon Jul 22, 2025
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as
Staleto make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough:+1. Thank you for your contribution!