I'm trying to figure out how to get Harvest data into our "central" VictoriaMetrics instance and I'm having a difficult time figuring out what I need to configure in the /etc/nabox/harvest/harvest.yml Docker Compose file and/or if I just need to bind the ports being used by the "internal" VictoriaMetrics scraper to the host. All of our other monitoring goes to a central VictoriaMetrics instance and Harvest is off to the side and I'd like to get away from that. I apologize if I'm butchering terminology and I'm happy to provide config examples and clarify anything.
#Harvest in NABox - External Prometheus/VictoriaMetrics Scraper
void oyster
tropic quail
Hey Jason, replying here so anyone can benefit. Latest NAbox versions have a proxy mode to get directly to the harvest scraper from outside, that should do it, let me check how it works
void oyster
25.05.1?
That certainly sounds perfect 🙂
Is there documentation on it, or should it be obvious in the UI after upgrading?
tropic quail
Nothing obvious, and of course, no documentation 😄
Hit the following endpoint : https://nabox/havrest/proxy/12990/metrics
for each port declared in harvest.yaml
void oyster
Finally got around to testing and I can confirm that http://<nabox_hostname>/havrest/proxy/<poller_port>/metrics is queryable from the outside
Thank you very much, @tropic quail
opal mango
Hi @tropic quail is havrest a typo in the url or by intentionally?
lime falcon
previously, Yann mentioned that he named it havrest by design. It does seems like that name confuses folks
opal mango
Good to know, was asked already by the team 🙈