Closed Tieske closed 3 years ago
@fffonion @hbagdi please check this one carefully, I'm not enough into Prometheus to know whether not-initializing actually poses an issue (some others were not, so I assumed it to be ok).
this builds on top of the other PR, which has non-controversial fixes.
The only consistent failure remaining is the one against Kong master
branch. The fix for that one is in https://github.com/Kong/kong/pull/7529
I think technically having consistency is good, but since prometheus.lua
is a vendored 3rd library, I don't
feel it's a good idea to diverage its behaviour here from the upstream.
@Tieske How about we initialize kong_enterprise_license_errors
instead, Will that solve the problem here?
How about we initialize kong_enterprise_license_errors instead, Will that solve the problem here?
that was the alternative, didn't know the lib was "vendored".
replaced by #144
The problem was with
kong_enterprise_license_errors
.kong_enterprise_license_errors
was not initialized, but was tested to be0
, this caused the CI failure.kong_nginx_metric_errors_total
was initialized, and tested to be0
For consistency the following changes were made:
kong_nginx_metric_errors_total
no longer initialized0