[Fullstory] Enable reporting when running from source

[lizozom]

At the moment, fullstory is enabled and reporting only when running on cloud.
We'd like to leverage fullstory's capabilities to improve our own developer experience.
In order to do that, we want to enable fullstory when running kibana locally in dev mode (!isKibanaDistributable).

Ideas:

• We need to set an env var to allow user segmentation (dev: true?)
• Should we move the integration code outside of the cloud plugin?
• Find out what domain we need to enable on fullstory admin for the data to be recorded

[elasticmachine]

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

[afharo]

#121992 will already move the piece of logic to a package.

However, don't we need special configuration like the org_id for Fullstory to work?

[afharo]

@lizozom developers can now enable it by setting:

xpack.cloud.id: "elastic_kibana_dev"
xpack.cloud.full_story.enabled: true
xpack.cloud.full_story.org_id: "<FullStory's Org ID>"

Is the request to enable it by default in development mode? I'd like to understand the benefit we'd get if we did that. I wonder if it'd create more noise than anything. I'm thinking about developing a feature and it crashing: those errors will be reported to FullStory even when they are not really that important because the developer is taking care of them as part of their own development cycle & testing.

[lukeelmers]

I'd like to understand the benefit we'd get if we did that. I wonder if it'd create more noise than anything

++ Agreed, it isn't clear to me what concrete benefits we'd get from doing this, and we'd be using up our FS sessions for it. IMO tools like buildbuddy are better suited to answer questions about the DX in Kibana.

I'm going to go ahead and close this issue for now. If you disagree, feel free to reopen so we can discuss @lizozom