-
Type:
Task
-
Resolution: Won't Do
-
Priority:
L3 - Default
-
None
-
Affects Version/s: None
-
Component/s: backend
-
Not defined
Context:
Since our telemetry reporting will not throw any errors (only info logs) if we receive an unexpected response/error after sending our telemetry data to shared services, we will not know if something changed that results in our current implementation failing to report telemetry data regularly. To ensure we regularly check if the telemetry data Optimize sends is received correctly by shared services, we should consider either adding a jenkins job or a stage for our branch builds that sends some test data (either to the integration endpoint shared services hosts or a local telemetry deployment).
AT:
- A jenkins job or branch build stage exists which tests our telemetry reporting