Thanks for the detailed report. With regards to the Total Connections being empty: we removed the metric because it was a bit meaningless but we forgot to remove the item from the UI. I have a pull request open to fix this. I will run some tests for the Current Connections metric.

I can't seem to reproduce this. I fired up an RTRclient instance on a test machine and Routinator correctly shows one connection. Connecting a second RTRclient from another machine makes Routinator show two.

I am pretty sure it initially did show the single RTR connection just fine. I was looking at the stats when this was deployed and I think I'd noticed if it was 0. I suspect some time later that connection was "lost"...

I will keep an eye on this especially when restarting next time (might not happen until update to next version, unless doing so helps debugging somehow).

I have observed the issue in two cases (with 0.11.3). In both cases the RTR connection probably was not terminated cleanly as the routers involved could not longer reach the routinator instance. The counter was correctly decremented.
But when the connection was restored, the counter did not increment again.

@birkschroeder Oh, this is helpful! Thank you!

I think I fixed the issue in #811 and thus in 0.12.0-rc1, but since I was never able to reproduce it, I am not entirely sure. I will close the issue now, but please do re-open it if the problem persists.

@partim I am facing this issue on the Routinator v0.12.1.

situation:

• Routinator is having 2 RTR Clients(BIRD v2.08) but displays 0 current connections on bashboard.
• The clients are connecting using IPv4 private IPs.

If you would like me to publish a new issue, please let me know.
thank you.

No need for a new issue, I’ll just re-open this one.

I’m starting to think Bird is the common denominator of all the reports. We will create a test setup and see if we can replicate the issue.