Quarkus Rest End Points work on the RestEasy framework and the filters and interceptors work only where RestEasy is involved.

There are other end points that Quarkus exposes which bypasses all these filters and interceptors, namely, /q/metrics or all /q/ routes.

These are Vertx Routes which operate on the Vertx framework and the filters applied on RestEasy do not apply here. The guide to creating Vertx Routes is here : https://quarkus.io/guides/reactive-routes

More Details and Full thread here : https://github.com/quarkusio/quarkus/discussions/46144