{"task": {"agent_timeout": 3000, "task": "testgen__jaegertracing__jaeger-6733", "verifier_timeout": 3000, "instruction": "The following text contains a user issue (in <issue/> brackets) posted at a repository. Further, you are provided with file contents of several files in the repository that contain relevant code (in <code> brackets). It may be necessary to use code from third party dependencies or files not contained in the attached documents however. Your task is to identify the issue and implement a test case that verifies a proposed solution to this issue. More details at the end of this text.\n<issue>\n      Similar to #6606\n\nJaeger-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.\n\nThis will need to be done with some reverse engineering of the UI code base because there is no other point of reference of what the data format should be. The main component in the UI is `packages/jaeger-ui/src/components/QualityMetrics/*`. An example of a valid URL is `/quality-metrics`, but there may be other parameters.\n\nThe code that generates the real data can be found in https://github.com/jaegertracing/jaeger-analytics-flink.\n\nA successful validation will be:\n\n* running Jaeger, e.g. `go run ./cmd/jaeger`\n* navigating to `/quality-metrics` in the UI to see the data\n\nWe should also add a check to the all-in-one e2e integration test that would query the same endpoint in the UI and get back some sensible result.\n\n</issue>\nPlease generate test cases that check whether an implemented solution resolves the issue of the user (at the top, within <issue/> brackets).\nYou may apply changes to several files.\nApply as much reasoning as you please and see necessary.\nMake sure to implement only test cases and don't try to fix the issue itself.\nYou are not allowed to read git history.\n", "memory": "8192m", "runnable": false, "difficulty": "hard", "language": "", "cpus": "", "instruction_truncated": false, "category": "test-generation", "compose": false, "has_solution": true, "oracle": null, "docker_image": "", "taskset": "devopsgym", "tags": ["test-generation", "devops-bench"]}, "runs": []}