Loading...

XML

Word

Printable

Story Points:
1
Epic Link:
Phase 2: Usage metrics
Blocked:
False
Ready:
False
Acceptance Criteria:

Hide

A secret containing the Segment key is available in the redhat-ods-applications namespace for all new installations of the RHODS add-on.

We should also have a plan in place to set it up for existing RHODS installations.

Show
A secret containing the Segment key is available in the redhat-ods-applications namespace for all new installations of the RHODS add-on. We should also have a plan in place to set it up for existing RHODS installations.
Automated:
Yes
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Fixed in Build:
1.8.0-6
Regression:
No
Release Note Text:
Undefined
Status Summary:
Need resolution of admin opt in approach
Target Release:

RHODS_1.8.0_GA
Test Blocker:
No
Test Coverage:

Yes
Watchlist Impact:
None
Git Pull Request:
https://github.com/red-hat-data-services/odh-deployer/pull/200
Market:

Sprint:
IDH Sprint 4, IDH Sprint 5, IDH Sprint 13, IDH Sprint 14, IDH Sprint 15, IDH Sprint 16, IDH Sprint 17, IDH Sprint 18

The User Interaction Telemetry tracking will require a segment key to be available in the RHODS namespace.

This key needs to be placed in an OpenShift secret. The contents of the key are considered public and can therefore be stored in Git in plaintext.

See this document for the details on how we came to this decision as well as ~~RHODS-1503~~ for more context.

blocks

RHODS-1810 Recurrent "HTTP request failed" error in dashboard pod's log

duplicates

RHODS-1810 Recurrent "HTTP request failed" error in dashboard pod's log

is blocked by

RHODS-2856 Ability for admins to opt in/out of user interaction tracking

RHODS-658 SPIKE: Design a solution for allowing customers to opt-into user workload telemetry data

RHODS-2434 [UX] Design user interaction opt-out for Add-on flow

relates to

RHODS-2942 Author new test cases to verify automatic creation of segment.io key (User telemetry)

(1 relates to)