openstack_nova_security_groups metric unavailable

[icinga1312]

exporter errored with
ERRO[0036] Failed to collect metric for exporter: nova, error: failed to collect metric: security_groups, error: Resource not found: [GET https://my.domain.cloud:8774/v2.1/os-security-groups], error message: {"itemNotFound": {"code": 404, "message": "The resource could not be found."}} source="exporter.go:123"
nova droped '/os-security-group*' since 2.36 api microversion
https://docs.openstack.org/nova/wallaby/reference/api-microversion-history.html#id33

maybe openstack exporter should drop the metric too

nova: wallaby
openstack-exporter: 1.4.0, master

[Hybrid512]

Not pretty sure that most of the Openstack clusters installed out there are all >=wallaby.
Would be better to return some null value (0, -1, ... anything else) in case of error from gophercloud instead of throwing an error of that kind.
Or maybe support Openstack versioning and deprecations in the API but it would mean a lot of work and this is useless since the exporter rely on gophercloud which should do it already.

[gtherond]

This endpoint was dropped with 2.36 microversion, even Victoria clusters are impacted.
I'm currently on victoria with some of ours.

[priteau]

Please note that you can set OS_COMPUTE_API_VERSION as an environment variable to get this metric to work again.

[gtherond]

Please note that you can set OS_COMPUTE_API_VERSION as an environment variable to get this metric to work again.

Yes, you're right, but I don't understand where it fit with this issue? We want the exporter to target the latest API for compute while still getting the security group (not the old os-security-group api endpoint which is deprecated) list, by using the env var we won't benefit from the latest data/information available with API.

Or did I missed something?

[mstinsky]

I just ran into the same issue as this here, aswell as #249.

Are we really meant to pin the microversion for the exporter? If so I think the exporter should pin itself inside the api calls, shoulnd it?

EDIT:
I just had a look into the microversion releases, nova microversion 2.36 is newton release. So this is deprecated since a long time. I would argue that its not the worst idea to just remove those from the exporter.

[mstinsky]

Please note that you can set OS_COMPUTE_API_VERSION as an environment variable to get this metric to work again.

Another side node for this. Pinning the microversion is not possible in this case as the api was completely removed with openstack ussuri.

[gtherond]

I actually use ZED and put the microversion using the environment variable, but as openstack API gives a way to discover available and supported version, we shouldn't have to do that when looking to target the currently latest available version on the targeted cloud.

We should use that feature only when targeting either OLD/DEPRECATED or EDGE version that aren't yet considered as prod version.