Open mcsammac opened 4 years ago
Hi @mcsammac, we do scrape some metric from /nitro/v1/config. But, in general, preference is for /nitro/v1/stat as it helps to avoid per config entity fetch which is a lot slower and susceptible to timeouts if config is huge as, then, we have to iterate per config entry. Are you looking for any particular config ?
@mcsammac Any update on this requirement?
Hello @aroraharsh23 sorry i missed you original comment. The one that we were particularly interested in was cmppolicy. We were wanting to get information about the usage of our individual compressions policies.
Would be cool to have config/nslicenseserver also, especially:
name | type | ro | description |
---|---|---|---|
status | Double | Read-only | Status of license server. |
grace | Double | Read-only | Grace status of server. |
gptimeleft | Double | Read-only | Grace time left. |
any update on this maybe?
Hi @aroraharsh23, we are looking for info from nslimitidentifier config such as Threshold, Timeslice, Traps, Hits, Action Taken.. etc. Is it possible to include this?
Thank you users for trying out metrics-exporter and providing your product requirements. We have Citrix Observability exporter - COE (https://github.com/citrix/citrix-observability-exporter) as an alternative to Metric-exporter and we will aim to support nitro-configs telemetry through COE in future.
Currently only stats can be obtained from /nitro/v1/stat, but there are other metrics that would be beneficial that can only be obtained from /nitro/v1/config/. It would be awesome if there was a way to specify in the config file to obtain a stat from the config endpoint.