omada_exporter icon indicating copy to clipboard operation
omada_exporter copied to clipboard

Omada Exporter Metrics Page Infinite Loading After Updating Controller from Version 5.9.9

Open baltineu opened this issue 1 year ago • 2 comments

Hello,

After updating our network controller from version 5.9.9 to 5.14.26.1, we've encountered an issue with the Omada Exporter; specifically, the metrics page is not functioning as expected.

Previously, with the controller version 5.9.9, the Omada Exporter was operating normally. However, post-update, while we can access the Omada Exporter's web interface without any problems, navigating to the metrics page results in an infinite loading scenario without any metrics being displayed.

Additional Information:

  • The issue persists even after restarting the Omada Exporter and the controller.
  • No network changes were made besides the controller software update.

I am wondering if there are any compatibility issues with the new controller version or if there is a potential bug that needs addressing. Any guidance or support on this matter would be greatly appreciated.

Please let me know if any additional information or logs are required to assist in diagnosing the issue.

baltineu avatar Sep 12 '24 15:09 baltineu

I have the same issue with version 5.15.8.12. Does anybody have a workaround already?

SI-Patrick avatar Feb 13 '25 18:02 SI-Patrick

I have debugged a bit. The metrics request does end and return successfully some metrics. But it takes a lot of time, because of the port collector's requests to omada. The request time depends on the number of switches/ports (for me there are 10 switches, it takes 8 minutes to complete).

Image

SI-Patrick avatar Feb 13 '25 19:02 SI-Patrick

just want to mention that i am also seeing this behavior.

i am running an OC200 which is very slow to begin with, but i highly doubt running the software controller would speed things up enough to shave off several minutes of time.

it's hard to know if this is a result of inefficiencies in the omada API or the exporter code itself. hypothetically if you could persist the connection for long enough to collect all the data, you could leverage the pushgateway to set up some a path for collecting the exporter data. personally i think doing that would be kinda cursed.

crutonjohn avatar May 20 '25 20:05 crutonjohn