upcoming: [M3-7861]: Include powered-off data in clone analytics event

[hkhalil-akamai]

Description 📝

Updates the Create Linode analytics event when cloning to include whether the source Linode was powered-off.

Target release date 🗓️

4/15

How to test 🧪

• Enable the Linode Clone UI Feature flag
• Go to http://localhost:3000 and turn on analytics logs for Adobe:
  • Ensure REACT_APP_ADOBE_ANALYTICS_URL is set in your .env
  • In the browser console, type _satellite.setDebug(true)
• Clone a powered-on/off Linode
• Verify the Create Linode event is fired and the data.isLinodePoweredOff field reflects the power status of the origin Linode
• Optional (it takes about ~1 hr for Adobe dashboards to update):
  • Log into Adobe Analytics
  • Go to the Projects folder and open the Linode Cloud - Dev Dashboard. Scroll down to the bottom two graphs, "Component Details vs. Component Clicks" and "Number of Events With Linodes Powered Off" and observe the data before and ~1 hour after your testing, which should now include metrics for your event(s) that fired.

As an Author I have considered 🤔

Check all that apply

• 👀 Doing a self review
• ❔ Our contribution guidelines
• 🤏 Splitting feature into small PRs
• ➕ Adding a changeset
• 🧪 Providing/Improving test coverage
• 🔐 Removing all sensitive information from the code and PR description
• 🚩 Using a feature flag to protect the release
• 👣 Providing comprehensive reproduction steps
• 📑 Providing or updating our documentation
• 🕛 Scheduling a pair reviewing session
• 📱 Providing mobile support
• ♿ Providing accessibility support

---

[hkhalil-akamai]

@mjac0bs While we wait on changes on the analytics side, I wanted to prototype what custom analytics key-value pairs might look like based on my understanding of the changes.

[mjac0bs]

Thanks for prototyping this! As I played with this locally, I actually wasn't seeing the event fire with data (after I changed it from details) like I would expect, so I've let Richa know and will follow up with what she says -- I think there's probably still a misconfiguration on the backend because we can do something like this:

In the meantime, I'm leaving some thoughts here.

[mjac0bs]

This is looking good from local testing with the changes in the Adobe dev environment! Approving pending my couple of additional comments re: variable name and tracking isLinodePoweredOff for events other than clone.

Clone with Linode Powered On	Clone with Linode Powered Off

While it takes about 1 hour for event data to show up in the AA dashboard, I did set up a graph in the Linode Cloud - Dev Dashboard and can see that our new custom component data is being associated with their respective click events:

[github-actions]

Coverage Report: ✅
Base Coverage: 81.78%
Current Coverage: 81.78%

[mjac0bs]

@hkhalil-akamai I'm going to use M3-7964 to update our documentation on Adobe in our developer guide to reflect the latest changes.

[mjac0bs]

I'm going to go ahead and merge this. e2es failed on the final runner because of the hanging test in account-switching.spec.ts. This test is a known issue, unrelated to these PR changes.