HotCodePush

telemetry-export-delivery

Find failed telemetry export deliveries with hotcodepush telemetry-export-delivery list and send one again with hotcodepush telemetry-export-delivery redeliver.

hotcodepush telemetry-export-delivery lists and repeats the deliveries of the organization's telemetry export: one log record or one metrics document, with its status, its attempts and the backend's answer. The retries and how long the rows are kept are on Telemetry export.

list

List the export's deliveries, filtered by status and time. --status failed --created-since 2h finds the ones to send again after an outage of your backend.

OptionTypeDescription
--created-since <time>stringThe earliest delivery, inclusive: an ISO 8601 timestamp or a duration ago such as 2h or 7d.
--created-until <time>stringThe latest delivery, inclusive: an ISO 8601 timestamp or a duration ago such as 2h or 7d.
--limit <count>numberHow many to list, at most 100; 50 by default.
--offset <count>numberHow many to skip: the offset the previous page ended with.
--status <status>failed | pending | succeededfailed, pending while it is retried, or succeeded.
hotcodepush telemetry-export-delivery list --status failed --created-since 2h
hotcodepush telemetry-export-delivery list --organization Acme --json

redeliver

Send a delivery again, once, and print the backend's answer. A pending delivery is taken from the retries. A log record goes out as it was, and a metrics document carries the current numbers. Confirms once (--yes in a script).

OptionTypeDescription
--delivery <id>stringThe delivery, by id, as "hotcodepush telemetry-export-delivery list" prints it.
hotcodepush telemetry-export-delivery redeliver --delivery 9a4f2e71-3b8c-4d65-b1e7-0c2d5f8a6e93
hotcodepush telemetry-export-delivery redeliver --delivery 9a4f2e71-3b8c-4d65-b1e7-0c2d5f8a6e93 --yes --json

Last updated on

On this page