search

zalando / skipper

An HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress
https://opensource.zalando.com/skipper/
Other
3.07k stars 347 forks source link

Status endpoint with list of filters and predicates #222

Open mo-gr opened 7 years ago

mo-gr commented 7 years ago

Skipper can be extended with custom filters and predicates at compile time. This is a great feature.

But it would be really helpful to have a status endpoint (maybe on the debug listener?) that enumerates all filters and predicates, which are known to that specific instance of skipper.

lmineiro commented 7 years ago

This could be enriched with #132. I'd expect the version and some kind of host identification to be present in that output

sarslanhan commented 7 years ago

This could be closed as #267 was merged.

lmineiro commented 7 years ago

Isn't #267 just reporting the filter and predicates for a single route? I thought this issue was about getting a list of the compiled (available) filters and predicates. @mo-gr ?

sarslanhan commented 7 years ago

@lmineiro @mo-gr I had the idea that debug listener is returning info about a single request. This is why I thought it could be closed. But then if that is the case the idea is different and maybe status endpoint or something else would make more sense.

szuecs commented 6 years ago

@mo-gr We have now support for plugins that are loaded at start time. Should these also be listed?

ruiaraujo commented 6 years ago

If possible I would say yes.