Good morning; new here, so please excuse/correct any local forum etiquette gaffes…
I have a fairly recent setup that is working. However, it’s working optimally for other services, but not for feeding to FA.
Setup:
Debian bullseye on amd64
dump1090: docker container from jraviles/dump1090 (working well, dump1090 container only, not using the companion containers in the docker compose file)
Right now everything is connecting and feeding to FA without any errors in any logs. The problem is, piaware is only feeding about 1% of my received messages. I also feed to adsbx, and am getting the full feed rate there - I’m seeing about 150-160 messages/sec on my local dump1090 status page, the same 150-160 on my adsbx page, and only about 1.5-2.0 m/sec on my FA device page.
To back up that lots of messages aren’t getting through, all three pages (local, adsbx, FA) are seeing about 28-30 planes at the moment, but the FA page has average last seen times of 10-30 seconds where the other two are mostly 0-1.
I’m new to piaware but pretty comfortable with linux, so perfectly happy to get down into the weeds, I just don’t know PiAware itself enough to know where to start digging. Any suggestions?
Are you looking at the local view from the statspage of your setup or on the skyaware anywhere page ? Skyaware Anywhere has a lower sampling rate then the local view.
Those are what I’m comparing, yes. It sounds like there’s a chance the different sample rate I’m seeing is intentional, then? I was assuming the low sample rate on SkyAware Anywhere reflected FA not receiving all my data.
What confirmed that in my mind was this log line (similar in all instances):
May 07 09:58:48 felix piaware[670486]: 29007 msgs recv'd from docker-prox (523 in last 5m); 28995 msgs sent to FlightAware
At my local receive rate right now, I am getting roughly 30-40,000 messages per five minute interval. My read of that log is that PiAware is only pulling about 2% of that to forward to FA (523 in that interval). I do know my adsbx forwarding client is forwarding all 30-40k.
The local view will show you the actual receiving rate locally. The sample rate for the Skyaware Anywhere is indeed lower since this data is first sent to the servers and then transported back. This delay is part of the reason you can see less aircraft in the Skyaware Anywhere view.
The sampling uploaded to the servers is also depending on the previous sent data as far as I know. If the timing isn’t exactly matched then the number of messages reaching the servers can be lower.
On average my upload rate is 18% towards the servers, and around 3000-3500 positions per 5 minutes.
Got it, thanks! I will assume all is well for now, and leave everything as is - that should let things settle down for at least 30d to see where I land.
