[Onboarding] Add telemetry events

[mykolaharmash]

Events:

• User clicks on the Firehose card (this should include service provider (AWS, GCP, Azure) where user's stack is deployed, this depends on this task)
• We start to monitor for incoming data
• Separate event for every identified index with data
• User clicks on one of the suggested CTAs after data has beed received

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[elasticmachine]

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

[akhileshpok]

@mykolaharmash - This is looking good! We need to report the time it takes to complete the workflow successfully as well. Thanks

[akhileshpok]

@mykolaharmash - Can you please work with @marcogavaz from the BI team to define a funnel and corresponding EBT events for this new onboarding flow? Marco is already working with Justin on a similar task for the new Hosts and K8s quickstart flows. Thanks

[elasticmachine]

Pinging @elastic/obs-ux-onboarding-team (Feature: Observability Onboarding)

[mykolaharmash]

@marcogavaz Here is a table with all CTAs at the end of the flow.

Each CTA link can have 3 different formats that we need to parse:

• observabilityOnboardingDataIngestStatusActionLink-dashboard-aws-80ed1380-41a6-11ec-a605-bff67d9b7872 for CTAs that lead to one of the dashboards
• observabilityOnboardingDataIngestStatusActionLink-discover-AWS/S3 for CTAs that lead to Discover
• observabilityOnboardingDataIngestStatusActionLink-logs-explorer-awsfirehose for CTAs that lead to Logs Explorer

General format is observabilityOnboardingDataIngestStatusActionLink-<DESTINATION_TYPE>-<DESTINATION_ID>, where:

• DESTINATION_TYPE is one of: dashboard, discover, logs-explorer
• DESTINATION_ID is either a dashboard id like aws-80ed1380-41a6-11ec-a605-bff67d9b7872 or a dataset name like AWS/S3