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

[Azure][container_registry] Metrics with PT1H time grain problems #7646

Open
tetianakravchenko opened this issue Sep 4, 2023 · 1 comment
Labels

Comments

@tetianakravchenko
Copy link
Contributor

tetianakravchenko commented Sep 4, 2023

Problem 1.

Metrics with PT1H time grain are scraped/stored every 5 minutes with 1 hour of delay:

Screenshot 2023-09-01 at 12 07 59

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:

Screenshot 2023-09-01 at 16 19 59

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

@tdancheva
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants