-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Telemetry] Remove from
and to
timestamps from usage stats APIs
#81579
Conversation
@elasticmachine merge upstream |
… telemetry/optional_to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for stack monitoring. It seems you only touched your files in the monitoring plugin
x-pack/plugins/monitoring/server/telemetry_collection/get_cluster_uuids.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/monitoring/server/telemetry_collection/get_all_stats.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/monitoring/server/telemetry_collection/get_high_level_stats.test.ts
Show resolved
Hide resolved
x-pack/plugins/monitoring/server/telemetry_collection/get_kibana_stats.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for tackling this!
It works as it is right now but we should be using the monitoring/common/constants.ts
file for all the hard-coded time intervals, like we do for the TELEMETRY_COLLECTION_INTERVAL
. That way we can keep them in one place and document each value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you for doing this 🧡
💚 Build SucceededMetrics [docs]page load bundle size
History
To update your PR or re-run it, just comment with: |
All requested changes addressed. Approved by @afharo
…lastic#81579) Co-authored-by: Kibana Machine <[email protected]> # Conflicts: # x-pack/test/functional/apps/infra/home_page.ts # x-pack/test/functional/apps/infra/logs_source_configuration.ts
…APIs (#81579) (#82266) Co-authored-by: Kibana Machine <[email protected]> # Conflicts: # x-pack/test/functional/apps/infra/home_page.ts # x-pack/test/functional/apps/infra/logs_source_configuration.ts
…e-details-overlay * 'master' of github.com:elastic/kibana: (72 commits) [CCR] Update README.md on how to start 2 clusters for testing (elastic#81487) [APM] Scale transaction rate correctly (elastic#82155) Upgrade to hapi version 18 (elastic#80468) [Uptime] Remove custom handling of license enabling (elastic#82019) [Telemetry] Remove `from` and `to` timestamps from usage stats APIs (elastic#81579) Enable send to background in Vega (elastic#82229) Enable send to background in Timelion (elastic#82232) [Actions & Connectors] removes Connector flyouts after usage (elastic#82126) Add derivative function (elastic#81178) [Discover] Deangularize context_app.html, part 3 (elastic#81838) [Visualize] Vis listing page breaks on unknown vis type (elastic#82018) Rename `batchSize` parameter to `batch_size` to be consisten with the API namings guidelines. (elastic#82123) Minor edits in Single Metric Viewer (elastic#82159) [Actions] Fix type contract (elastic#82168) Upgrade EUI to v30.1.1 (elastic#81499) Skip failing ES snapshot test (elastic#82207) Skip ES snapshot failing suite (elastic#82206) [Alerting UI] Grouped list of alert types using producers in Types filter of Alerts tab (elastic#81876) [Maps] convert vector style component to typescript round 1 (elastic#81961) Fix link to upgrade assistant (elastic#82138) ...
The usage api now accepts a
timestamp
string or unix timestamp number. The api no longer accepts aTimeRange
parameter.Restrict
from
andto
usage to only inside monitoring collection where it is used.Increase fetching Cluster_uuid query timestamp difference from 20 minutes to 3 hours. Currently if a cluster has not reported anything in the last 20 minutes then we do not send any data related to that cluster. Increasing the query from 20 min to 3 hours provides better guarantees on capturing all the connected monitoring clusters.
This change makes it easier to work on alejandro's RFC to completely decouple monitoring from telemetry.
Closes #57782