fabio
fabio copied to clipboard
fabiolb
setting `registry.consul.tagprefix` doesn't seem to work
I'm trying to use the registry.consul.tagprefix config value to change the default urlprefix- to fabio-. I have services in consul passing health checks and registering service tags of the form fabio-... but when I run a Fabio instance with the tag prefix set to fabio- it doesn't find any services.
@far-blue does it work if you use the default? I'm successfully using this feature in all my deployments, even with the latest stable release (v1.6.0). Are there any logs in fabio related to the tags or the config?
The default 'urlprefix-' prefix works fine and I've been using fabio in production for a few years now. I was actually wanting to setup support for a 'uat' environment for testing out changes to fabio config on production infrastructure but without interacting with production services so thought changing the tagprefix would be a nice approach.
When using a non-default tag prefix, are there any useful logs or info you can find in fabio to confirm why that isn't working?
no, no logs. Everything appears to be working correctly but fabio simply doesn't "see" any services to route.
@far-blue we're using this feature in production as well (overriding registry.consul.tagprefix for some fabios). Can you help come up with a minimal environment that demonstrates this issue? can you try setting the log level to TRACE ? That might shed some light.
