Instrument app with Google Analytics - DRAFT

[kdhamric]

In order to measure and make improvements to Tracetest, we need to have analytics.

Testkube has implemented analytics with GA, so we should get their advice to learn from their successes / mistakes. Ken is talking to Bruno on 4/19/22 and will update this card based on the conversation. We should look at their code and possibly 'borrow' from it - I believe this is one of the files involved: https://github.com/kubeshop/testkube/blob/0a91e4aa58eeeb2c0f8408ce0a671e5f2824b5bc/cmd/kubectl-testkube/commands/root.go
We can ask to see if we can have the person that implemented give us advice / share any development they did.

Each install of Tracetest will want to have a UUID tied to it. We will pass this anonymous id with GA to associate usage with a particular install.

There will be two GA accounts we will be sending data to:

• one for the Tracetest Demo
• one for all other installs of Tracetest
  We need some way to let our Demo know to use the Demo specific account.

We will want to capture typical usage metrics, and will need to follow GA process for SPA (https://developers.google.com/analytics/devguides/collection/gtagjs/single-page-applications)

In addition, we will want to instrument certain events using rich descriptions (ie disable-analytics vs just disable - make it obvious as the people looking at the analytics will not know the code):
install-tracetest
uninstall-tracetest
disable-analytics
create-test
run-test
edit-test
add-assertion
edit-assertion
change-item-selectors (whenever selectorItems are altered from the default)
error-frontend - try to report the error

Ken will be updating this card over the next few days - lets not start this work until we have complete details recorded.