-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Send period in metricbeat data #12616
Comments
Nicolas had an old PR for doing the same thing: #6929 |
Thank you for opening, is there anywhere where we can read how you plan to use it? |
@exekias It would be a solution to the problem outlined in elastic/kibana#36774 |
@exekias If the period is stored with the event data then we would need to get a sample from the time range. Either using an aggregation (terms?) or just plucking the last document where the field exists (along with filtering for time range and whatnot). |
As discussed yesterday: In order to detect gaps, it would be nice to have the reporting period in docs. The UI can then query for the max period across docs for some metric and use it as the minimum bucket size for the query. Then it will now that an empty bucket is a gap int he data. |
@sorantis FYI ^ |
Having the period as part of each event makes it possible for Kibana or ML to predict when the next event is potentially missing or delayed based on the period of the previous events. It can always be that the period changed but as soon as the next event comes in, this can be used as the new expected period. This field is not added to push fetchers, as they don't do periodic fetching. Fixes #12616 Co-authored-by: ruflin <spam@ruflin.com>
For querying metricbeat documents for the Kibana Infra UI app, it would be very helpful to know the interval in which data is sent by the various metricbeat modules.
One idea that came up in a call is to include the configured
period
in the documents themselves.The text was updated successfully, but these errors were encountered: