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.

Sign up for GitHub

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

Jump to bottom

[EBT][Server] V3 in-house shipper #125693

Closed
Tracked by #121992
afharo opened this issue Feb 15, 2022 · 1 comment · Fixed by #130696
Closed
Tracked by #121992

[EBT][Server] V3 in-house shipper #125693

afharo opened this issue Feb 15, 2022 · 1 comment · Fixed by #130696
Assignees
@afharo
Labels
Feature:Telemetry impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@afharo
Copy link
Member

afharo commented Feb 15, 2022 •
edited
Loading

Implement the V3 in-house shipper for the Server. We could reuse the leaky-bucket previously implemented in our POC.
We’ll need to add firewall detection (based on our current telemetry snapshot approach) and follow the current drop strategy Solutions teams apply (the “Default” as explained in T-1.4 in the Definition document).

In case of failure, for this MVP, we won’t implement any retry strategy for now. However, it will keep track of the count of errors and report it via the Snapshot Telemetry.
@afharo afharo mentioned this issue Feb 15, 2022
Closed
30 tasks
@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 15, 2022
@afharo afharo added Feature:Telemetry Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Feb 15, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Feb 15, 2022
@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Feb 15, 2022
@exalate-issue-sync exalate-issue-sync bot added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Mar 8, 2022
@afharo afharo mentioned this issue Apr 13, 2022
Closed
2 tasks
@afharo afharo self-assigned this Apr 14, 2022
@afharo afharo mentioned this issue Apr 20, 2022
Merged
2 tasks
@exalate-issue-sync exalate-issue-sync bot reopened this May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@afharo afharo

Labels
Feature:Telemetry impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[EBT] Add Elastic V3 Shippers afharo/kibana
[EBT] Add Elastic V3 shippers afharo/kibana
2 participants
@afharo @elasticmachine