heady basalt
Hi there, using NAbox with Prometheus 2.38 I wish to send limited scoped data to a customers Prometheus instance (?).
Have anyone done this before and can share how to configure it?
The customer also asks us if we support OAuth2 for this.
Sorry if I'm not using the correct terms here, new to this stuff.
steep jetty
for the most part Prometheus uses a pull model which means you scrape it instead of pushing. Can the customer scrape your Prometheus for what they need? In terms of oauth2, I see this but haven't tried it https://prometheus.io/docs/prometheus/latest/configuration/configuration/#oauth2
heady basalt
I guess scraping could be used, but can we limit the data they see?
steep jetty
I've not used it but https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_write can be used for that purpose
heady basalt
Ah yes! Remote write is what I want.
Anyone got experience with filtering out metrics for Remote write?
I guess I need to get down and dirty with the config files of Prometheus to set it up
and I guess any configuration changes made in Prometheus vill be overwritten upon upgrade of NAbox/Prometheus?
steep jetty
@untold knoll does nabox have a way to preserve prometheus conf changes across upgrades?
untold knoll
Yes, as long as everything is done in docker-compose.override.yaml
And the changes are done in prometheus cli arguments indeed
heady basalt
And this file is somewhere in the virtual appliance?
untold knoll
Yes there is some guidance on how to use this file here https://nabox.org/faq/#change-default-retention
It's not there by default