Post feeder reception stats to /api/feeders/reception#140
Merged
Conversation
Send feeder-attested reception stats (aircraft counts, max range, signal summary) from the forwarder's readsb JSON as a separate best-effort POST to the dedicated /api/feeders/reception endpoint, instead of folding them into the diagnostics payload. Rides the existing REPORT_STATUS consent and never affects the diagnostics result.
d4rken
force-pushed
the
feat/diagnostics-reception-stats
branch
from
c421402 to
8a8bda8
Compare
d4rken
changed the title
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
1 participant
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.
The feeder diagnostics push now also reports receiver-performance statistics — the aircraft a feeder is seeing, its maximum range, and a signal-strength summary — read from the forwarder's local readsb JSON.
These go out as a separate best-effort POST to the dedicated
/api/feeders/receptionendpoint rather than being folded into the device-health diagnostics payload, so the two telemetry lanes stay independent. The reception report rides the sameREPORT_STATUSconsent (an opted-out feeder sends neither), only fires when the forwarder has produced fresh data, and a failure never affects the diagnostics result.