Requirement

Changes are implemented in jaegertracing/jaeger#6607 to return dummy quality metrics. Fix the frontend to accomodate the changes according to the issue mentioned above.

Problem

Jaeger-UI has "hidden" capabilities, namely page that shows statistics about instrumentation quality in the deployed services. The corresponding server code was apparently never migrated out of Uber's internal code base. The proposal is to create the required endpoint in the jaeger-query but return some dummy data, which can later be extended with proper support for storage. The dummy data should use some obvious identifiers like sample-service-A, to make it obvious to the user that the data is not real. An alternative is to return just empty data but that is generally more confusing to the user.

Proposal

No response

Open questions

No response