Datadog tracks "go back to previous" link clicks on MHV Home

[wesrowe]

Description

User story

As a Cartography team member, I want DD to track the three "go back" link click actions on MHV Home separately, as well as the one on the temporary MR landing page, so that we can understand what area/content a Veteran was engaged with when they went back to MHV Classic.

Notes

• extending #85778
• Wes opened a support thread with DD on Fri, 6/14; @dcloud was CCed on those
  • UPDATE: actions are working as expected in Prod post-launch
• Current state of actions
  • Daniel added a custom action to the go-back link in the MR box
  • See "MHV-on-VA.gov Integration RUM" dashboard for a few funnels that capture the current state of these actions.
  • Note that the action names tracked in the dash are confusing, as they sometimes include more than just the text link – e.g., click on If you’re not ready to try the new My HealtheVet, you can use the previous version anytime. Go back... seems to include the whole second paragraph on MHV Home.

Possible tasks:

Acceptance criteria

• DD Actions are visible (in Prod and Staging) in DD for clicks on "go back" links on MHV Home and on the temp MR landing page
• We can tell in DD which link a given user clicked

[dcloud]

I have a meeting on 6/18 to discuss "missing clicks" with a Datadog technical support engineer

[dcloud]

As part of the support investigation with Datadog, it was suggested that we upgrade from v4 to v5, and I've been peeking at that. Currently Datadog is implemented platform/sitewide, so upgrading would either require:

• Upgrade for all teams, partner with platform to do so given this would affect all apps using DDG
• Yarn workspace-ification: I believe we could have our own package.json for the mhv-landing-page. Would need to evaluate feasibility and impacts, but it might be possible to upgrade DDG RUM only for our application.

Some notes on upgrading

• Upgrade RUM from v4 to v5

names of deprecated things

I put these lines in a file to grep for with rg (ripgrep)

removeUser
addRumGlobalContext
removeRumGlobalContext
getRumGlobalContext
setRumGlobalContext
addLoggerGlobalContext
removeLoggerGlobalContext
getLoggerGlobalContext
setLoggerGlobalContext
addContext
removeContext
proxyUrl
sampleRate
allowedTracingOrigins
tracingSampleRate
trackInteractions
premiumSampleRate
replaySampleRate
beforeSend

trackInteractions --> trackUserInteractions

Looks like many apps use the v5 name, usually alongside the v4 name…

delta -s --color-only <(rg trackUserInteractions -l vets-website | sort) <(rg trackInteractions $(rg -l trackUserInteractions vets-website) -l | sort)

Intake domains

https://browser-intake-ddog-gov.com is in devops, so I think we're good here

[dcloud]

Saving the DDG session search that shows the Prod events for the medical records card: @action.type:click "Medical Records Card":

[dcloud]

Also: @action.type:click @action.name:*Medical\ Records\ Card*, where the backslash escapes spaces and so we can perform a wildcard search on the action name. As opposed to the version in my previous comment which searches multiple fields, not just the action name

[dcloud]

Per support, going to switch from the attribute to a function call:

Next, from the screen recording, I see the data-dd-action-name attribute on the tag, but maybe we can try using the datadogRum.addAction() function here to add the custom click action. https://docs.datadoghq.com/real_user_monitoring/guide/send-rum-custom-actions/?tab=npm#instrument-your-code

[dcloud]

I forgot to move this into code review, but this got reviewed and is merged. Should be in staging shortly

[dcloud]

Seeing custom actions in DDG for staging, e.g. this event for "Click on Landing Page: Intro - Go back to the previous version of My HealtheVet"

[dcloud]

Not seeing actions recorded for the MR Transitional page aka "Click on Medical Records: Coming Soon…" link so far

[dcloud]

After merging the RUM config move to app-entry file, seeing the coming soon click action

@action.name:*Medical\ Records*

[dcloud]

It also looks like that config change may have fixed the bug with getting DD_RUM to output info in the console. I can run DD_RUM.getInitConfiguration() to see the config or DD_RUM.getInternalContext()?.session_id to get the session id

[dcloud]

While https://github.com/department-of-veterans-affairs/vets-website/pull/30605 appears to have made some of the console functions work, making it possible/easy to grab a session_id via DD_RUM.getInternalContext()?.session_id, there are remaining issues:

• signficant lag between actions taken in a session and events appearing in DDG. Need to reload datadog to see events appear
• The issues with labelling click actions on the "Learn More" content accordian
  • Opening the accordion appears to record sibling content: "Welcome to the new home for My HealtheVet. Now you can manage your health care needs in the same pla [...]" - @action.id:f1861868-b2dc-4ca5-b04a-20d87083d6d6
  • Closing grabs the content inside the accordion, per @action.id:1c375a4c-c7ef-4015-a282-198f9b1e43fb
• Possible double-counted click actions, e.g. @action.id:e9163295-a195-49c3-a20f-59f18f8bba8c -> @action.id:1976d1e0-8fdc-4811-9447-61540ddf68c3… I wouldn't expect to see the non-custom click being recorded any more on links that have the datadogRum.addAction call

Per my clicking around in staging - @session.id:2c298dca-f11a-4a8d-a42b-f53e4e1eb0d1

These observations should probably be put into a "Datadog debug" ticket if we need to continue to fix things with DD_RUM

[wesrowe]

@dcloud, did you make a "debug DD" ticket yet? I feel the work to add a custom action is a small price to pay for actions that make sense to anyone who looks! I would like to get @kat and @fmccaf1 thoughts on how these custom actions (to replace the buggy ones) should be labeled.