bclozel
commented
3 months ago Thanks for sharing.
Unlike most GraphQL schemas, the Actuator REST endpoints are:
- registered and exposed dynamically, which means that we cannot share a stable schema with GraphQL clients
- not connected as they don't share common types, unlike federated schemas where types are extended
- not graph-like nor property rich
Besides the ability to call multiple endpoints in one request, I don't see a lot of advantages in doing so. The Spring Boot team did consider other transports for actuator endpoints but the demand is quite low and plain HTTP seems to be the preferred approach in platforms.
I'm closing this issue for now.
So, I'm thinking it would be cool if actuator data could be consumed as part of a graphql query that gets built in if you have actuator on your classpath.
I don't currently have a real world use case, and perhaps it's a bad idea when it comes to federation. It's just an idea that I'm sharing.