Developer

 View Only
  • 1.  Help with Large Public Venue Dashboard on GitHub

    Posted 29 days ago

    So I was pointed to this as a starter by my SE. I have a VM deployed with docker installed and the up and running. Ran into one issue during the install where the build kept failing because a json lock file had yet to be created in the next-dashboard folder so the copy failed. I locally updated the dockerbuild file to not copy that file and to run "nmi install" instead for the "nmi ci" command and that fixed the issue.. I also put an issue into GitHub for it.

    However, this is not the problem I need to ask about. After the enviroment is up and running, I am blowing through my API allotment. From what I can tell, it appears that the setup is possibly requesting a new access token for every API request instead of re-using the token until it expires. 

    Is there any way to get some assistance on this, or is this GitHub deployment basically a best effort support?

    https://github.com/aruba/central-large-public-venue-monitoring-dashboard



  • 2.  RE: Help with Large Public Venue Dashboard on GitHub

    Posted 28 days ago

    Hi,

    May be open an issue or disccusions on github repo ?



    ------------------------------
    PowerArubaSW : Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP...

    PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...)

    PowerArubaCL: Powershell Module to use Aruba Central

    PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)..

    ACEP / ACMX #107 / ACDX #1281
    ------------------------------



  • 3.  RE: Help with Large Public Venue Dashboard on GitHub

    Posted 28 days ago

    Will do that. Opened one for he dockerfile issue, but after seeing no open or closed issues for the project, I was a little skeptical it would get any attention.




  • 4.  RE: Help with Large Public Venue Dashboard on GitHub

    Posted 28 days ago

    Hello!

    The developer that created this works on my team. I will send the thread his way to get some eyes on it.

    Cheers,

    Collin




  • 5.  RE: Help with Large Public Venue Dashboard on GitHub

    Posted 28 days ago

    Great!!!

    Thank you!!




  • 6.  RE: Help with Large Public Venue Dashboard on GitHub

    Posted 25 days ago

    Hi RW-7aafc2, I created the large public venue dashboard on GitHub, I am looking into the token creation.  Once I can find a fix for this, I will message you back in the thread!




  • 7.  RE: Help with Large Public Venue Dashboard on GitHub

    Posted 25 days ago

    Thanks Lucas.

    I also dropped in an issue with the dockerfile under the next-dashboard folder.

    Robert




  • 8.  RE: Help with Large Public Venue Dashboard on GitHub

    Posted 2 days ago

    Hi Robert, I have pushed a fix for the docker file build issue that you found on github!




  • 9.  RE: Help with Large Public Venue Dashboard on GitHub

    Posted 3 days ago

    So looking into this more, I do not think it is a token issue. Being new to Central, I wasn't looking at the dashboard correctly. It looks more like it is an issue with making calls too quickly. It is the calling rate chart that is showing all the fails.

    image



  • 10.  RE: Help with Large Public Venue Dashboard on GitHub

    Posted 2 days ago

    I have added a cache of the token based off of your initial question, and I spent some time last week making a few changes to the speed of API calls being made.  This can be manipulated by the number of multi-thread workers in the fetch.py file.  If you are running into a lot of failed API calls from too many concurrent requests, you can lower the maximum number of thread workers and increase the time interval for the script to run continuously on.  Try making those changes in the fetch.py file and see if you get an improvement in successful calls!