[FullStory] Document browser exposed config in the test #131527
Conversation
afharo
added
release_note:skip
| @@ -165,6 +165,7 @@ export default function ({ getService }: PluginFunctionalProviderContext) { | |||
| 'xpack.cloud.deployment_url (string)', | |||
| 'xpack.cloud.full_story.enabled (boolean)', | |||
| 'xpack.cloud.full_story.org_id (any)', | |||
| // No PII. Just the list of event types we want to forward to FullStory. | |||
There was a problem hiding this comment.
question: just for my own education (noob in FullStory) - are these just arbitrary strings, or Full Story has a predefined list of these events.
There was a problem hiding this comment.
These strings are not mandated by FullStory. This config is used to filter the events from EBT that we actually want to send to FullStory. It has a very aggressive rate limiting policy regarding custom events (up to 10 events per second and 30 per minute), so we want to send only the events from Kibana that we really want to have in FullStory. All the events will still go to our Remote Telemetry Service, it's just a filter to the FullStory endpoint.
Right now it's just ['Loaded Kibana'] because it's the only event we used to send to FullStory from the start. It may grow to match the name of the events we want to forward.
There was a problem hiding this comment.
Got it, thanks for the detailed explanation.
💚 Build SucceededMetrics [docs]
To update your PR or re-run it, just comment with: |
Summary
Follow up to #131148 to address NIT comment.
For maintainers