You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
We would normally do a telemetry review of the probes when we hit expiry, and plan to audit all the telemetry with Data Science in Q3, but need to bump the telemetry by 1mo because of code freeze for the Fenix Release.
data-sync-user
changed the title
Bump expiry for telemetry by 1 month for release
FNX2-16777 ⁃ Bump expiry for telemetry by 1 month for release
Aug 2, 2020
data-sync-user
changed the title
FNX2-16777 ⁃ Bump expiry for telemetry by 1 month for release
FNX3-15085 ⁃ Bump expiry for telemetry by 1 month for release
Aug 11, 2020
data-sync-user
changed the title
FNX3-15085 ⁃ Bump expiry for telemetry by 1 month for release
FNX-13063 ⁃ Bump expiry for telemetry by 1 month for release
Aug 11, 2020
data-sync-user
changed the title
FNX-13063 ⁃ Bump expiry for telemetry by 1 month for release
FNX2-16777 ⁃ Bump expiry for telemetry by 1 month for release
Aug 11, 2020
data-sync-user
changed the title
FNX2-16777 ⁃ Bump expiry for telemetry by 1 month for release
Bump expiry for telemetry by 1 month for release
May 19, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We would normally do a telemetry review of the probes when we hit expiry, and plan to audit all the telemetry with Data Science in Q3, but need to bump the telemetry by 1mo because of code freeze for the Fenix Release.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: