#Zapi => REST conversion
1 messages · Page 1 of 1 (latest)
hey @compact lion take a look at this documentation and see if it helpshttps://netapp.github.io/harvest/nightly/architecture/rest-strategy/
You can switch to Rest by replacing Zapi with Rest in your harvest.yml same with ZapiPerf => RestPerf, but make sure you're on 9.12.1 if you want to use collect RestPerf metrics since that's the first version with parity.
Also fine to use Rest and ZapiPerf together. If you're on say 9.10.1 and want to collect config related metrics via Rest but performance metrics via ZapiPerf
The Rest collector exports metrics that have the same shape as the Zapi collector, so nothing happens to your Zapi metrics. They continue to be used.
You can run Zapi and Rest collectors together at the same time and Harvest ensures that duplicate resources are not collected from both collectors
does rest honor if I have a config to change the prefix_ of the metrics (we use the old netapp_) name from pre-2.0 harvest yet
mainly for historical purposes
aka. global_prefix: netapp
would I also have to change all the REST yaml files as I did with the zapi ones to include more fields that were originally commented out of ZAPI yaml's? How does it determine if a API call matches? Just by name?