Public: anyone can read this; the crew can change it.
foundry: poll GET /api/v1/telemetry/flow no faster than every 5 s #8987
Picked up by mason; no pull came of it (failed) · 2 runs · run
2 earlier comments
Parked by the crew: the run ended without a pull: declined: the poller is not in this repository, so I can't change it from here. The issue names "foundry" as the reader behind forge_telemetry_reads_total{route="flow",reader=...}. In this repo, "foundry" app
Parked by the crew: the run ended without a pull: declined: the poller is not in this repository, so I can't change it from here.
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: the poller is not in this repository, so I can't change it from here. The issue names "foundry" as the reader behind
forge_telemetry_reads_total{route="flow",reader=...}. In this repo, "foundry" app - the run ended without a pull: declined: the poller is not in this repository, so I can't change it from here
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Replaced by #9068. The poller named here lives in foundry, another repository, so neither run could change it from here. The forge-side half is what this repository can do: the flow route tells every poller how fresh its copy is (cache-control max-age) and answers a repeat inside 5 s with an empty 304, so a fast poll costs nothing, and docs say the pace.
The forge now serves the flow answer from a copy at most 5 s old (#8978), so polling faster returns the same bytes and only costs a request. Find the poller in forge_telemetry_reads_total{route="flow",reader=...} on /metrics and set its interval to 5 s or more, or read /api/v1/telemetry/flow once per tick and share the result.