Document PacketRouterLivenessReport oracle data type - #2077
Merged
Conversation
Add a row to the Oracle Data File Format table for the new HPR gateway liveness report, which records when each gateway last connected and is uploaded daily to S3 as packet_router_liveness_report.<ts>.gz. The file lands under the foundation-iot-packet-ingest prefix (same internal helium-mainnet-iot-packet-ingest bucket as packetreport) and decodes with packet_router_liveness_report_v1 in packet_router.proto. Refs: - helium/helium-packet-router#337 (produces the report) - helium/proto#481 (adds packet_router_liveness_report_v1) - novalabsxyz/glacon-rs#43 (ingests the data type)
Deploying heliumdocs with
|
| Latest commit: |
a504ce4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f4213f5b.heliumdocs.pages.dev |
| Branch Preview URL: | https://docs-oracle-liveness-report.heliumdocs.pages.dev |
macpie
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds one row to the Oracle Data File Format table in
docs/network-data/oracle-data.mdxfor the new HPR gateway liveness report.foundation-iot-packet-ingestPacketRouterLivenessReportpacket_router_liveness_reportpacket_router_liveness_report.<unix_ms_timestamp>.gzservice/packet_router.proto→packet_router_liveness_report_v1Why
The helium-packet-router now tracks when each gateway last connected and publishes a daily snapshot to S3, mirroring the existing packet-report pipeline. This is a new decodable data type in the requester-pays bucket, so it belongs in the oracle data reference.
How each field was determined
hpr_gateway_liveness_reporter, which uploadspacket_router_liveness_report.<timestamp>.gzdaily.d79cbd9);packet_router_liveness_report_v1is at line 8 ofpacket_router.proto. The link is pinned to that merge commit since the message doesn't exist at the table's older shared commit. (The existingPacketReportrow stays pinned to its old commit, wherepacket_router_packet_report_v1was still at line 8 — it's now line 14.)glacon-rs-iot-livenesspipeline reads from thehelium-mainnet-iot-packet-ingestbucket, the same internal bucket as the existingpacketreportfiles, which surface underfoundation-iot-packet-ingest: novalabsxyz/ops-terraform-iot#18, novalabsxyz/ops-terraform-mobile-carrier#139, novalabsxyz/ops-fluxcd#669. Ingester: novalabsxyz/glacon-rs#43.Reviewer notes
helium-protoat the unmergedmacpie/liveness_reportbranch, and ops-fluxcd#669 notes the image tag needs bumping once a glacon-rs release with this type is cut — so data may not be flowing into the requester-pays bucket yet. The row is accurate for where it will land; happy to mark it forthcoming if preferred.