Use GraphQL to load error tracking detail page content
Problem to solve
We were previously loading frontend content on the error tracking detail page using our REST API. As we begin to support our engineering efforts to move away from REST, we should transition our page to use GraphQL instead so that we frontend can move faster and be less coupled with the backend.
Doing so will increase our feature velocity and cycle-time by removing backend requirements and coordination from future enhancements.
Intended users
This is a ~backstage improvement
Proposal
With the completion of #34943 (closed), we now have the ability to obtain the information we need using GraphQL to load the error tracking detail page. As such, we should replace the error tracking detail page to use our GraphQL API instead of our REST API.
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Kenny Johnston