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

[EBT] Allow list in FullStory shipper #131146

Closed
Tracked by #121992
afharo opened this issue Apr 28, 2022 · 1 comment · Fixed by #131148
Closed
Tracked by #121992

[EBT] Allow list in FullStory shipper #131146

afharo opened this issue Apr 28, 2022 · 1 comment · Fixed by #131148
Assignees
Labels
Feature:Telemetry impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@afharo
Copy link
Member

afharo commented Apr 28, 2022

We noticed that FullStory's rate limit of events falls too short for the number of events we foresee to generate from the UI.

This issue is to apply an allowlist of the custom events that will be sent to FullStory.

For now, the only custom event that will be sent is Loaded Kibana for backwards compatibility reasons.

@afharo afharo added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:Telemetry labels Apr 28, 2022
@elasticmachine
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Telemetry impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants