api

[wispy tulip]

When I follow the online NAbox docs, the NAbox should expose a REST API on /api/2.0/ and /havrest/2.0/ + Swagger interface.

Tried from local and remote system, I can call the namespace /api/1.0/ but it returns some general html code, whatever subspace you call, it always returns the same html.
In a browser, /api/1.0/ui/ does not return any page.
Then, when i try /api/2.0/ it returns 404 not found. Same for /havrest/2.0/ or the ui/ namespace. Nothing is there.
This was on a 4.0.8 version, newly deployed last week as ova on vSphere 8 env. Today, upgraded to v4.0.9 but it's still same behaviour.

On a version 3.5 NABox, I can see a container running registry.lab/nabox-api:latest. On the newer NAbox v4.0.x, no container for the api is seen?
Something off with my deployment? Or can i check some things to fix it?

[chrome frost]

Looks like the doc has a few errors. For NAbox, swagger is on /ui and for harvest it’s on /havrest/ui

[wispy tulip]

Okay it's working. Not exactly 100% what I was hoping for. We have some other Grafana running, and I want to get data from certain volumes from the NAbox. What method do you suggest? Expose the Prometheus and get the data there? I assumed we could hook onto the Harvest API and get some data there.