Open drmaciej opened 3 years ago
PRs welcome!
We have a routes endpoint which will include the management endpoints. You can have a ExecutableMethodProcessor<Endpoint>
bean, however you wouldn't have access to the logic that determines the URL, etc...
I'm aware of the routes endpoint, I was hoping for something with clickable links though. I'll have a look at the ExecutableMethodProcessor
, perhaps it takes me somewhere.
I have had a look; I may be able to come up with a PR soon; just need to figure out a bit more in terms of Micronaut internals.
Hi @jameskleeh, could I tackle this issue?
I'm thinking that the expected response should be like Boot's /actuator, like the following:
/actuator
Is this response format appropriate for the new endpoint?
@HerCerM Seems reasonable to me
@jameskleeh I've made a PR with a working implementation. I would like to know if I'm in the right direction before implementing the tests
I never got around to it - thanks @HerCerM!
Endpoints are described here https://docs.micronaut.io/2.3.3/guide/index.html#providedEndpoints. Boot has such a view at /actuator, enabled via EndpointLinksResolver and WebMvcEndpointHandlerMapping. A similar view would be very useful in Micronaut. In the meantime - until this does or does not become available - is there a way to discover all enabled @Endpoint-annotated classes, so I could build such a view myself?
Task List
Steps to Reproduce
Expected Behaviour
A management discovery endpoint, say /management, listing all available endpoints, together with their links, is available.
Actual Behaviour
This is not available.
Environment Information
Example Application