You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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 sameazure.resource.name
), but those 2 documents have different ingest time - that is 1 hour apart, one withSep 1, 2023 @ 15:15:34.000
and another withSep 1, 2023 @ 16:15:30.000
.Note that this behavior occurs only after > 1h of running this integration
cc @zmoog
The text was updated successfully, but these errors were encountered: