First push toward adding in-app telemetry

[echappen]

One issue with the current Stratos app is that there's no in-app telemetry that tells Cloud.gov what features people are using or how they're using them. If we don't have this information, we can't make informed decisions about the product or track success metrics. For these reasons, we want to include telemetry in the solution we're building.

Research what viable options exist in Cloud.gov's context for in-app telemetry, and how it could be implemented in our app. Also research any compliance limitations we may encounter.

The research should result in an ADR that 1) summarizes the findings, 2) proposes a decision on whether to use telemetry and, 3) if yes, proposes an implementation.

Prior art

previous Slack convo about OpenTelemetry

Acceptance Criteria

• [ ] ADR is shared with the team for feedback

[jduss4]

I started some research / findings about the technical and compliance aspects of telemetry in our google doc 🔐 , but I'm not certain that we're ready to write up an ADR until we can answer the question of what kind of information we want to collect. Once we know that, we can better follow up on the technical feasibility of capturing that information.