opensearch-project / opensearch-project/data-prepper
[BUG] Cannot get view in DashBoard - jaeger-hotrod
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
I get a x_content_parse_exception while triying .\examples\jaeger-hotrod Steps to reproduce the behavior:
- Go to localhost:8080 and click some buttons on Hot ROD page. 2. Open http://127.0.0.1:5601/app/observability-traces , select Data-Prepper and click refresh button
- See Error (details in opensearch-dasboard container) /***********
{"statusCode":200,"responseTime":8,"contentLength":9},"message":"POST /api/observability/trace_analytics/query 200 8ms - 9.0B"}
StatusCodeError: [parsing_exception] [term] query does not support [dispatchConfig], with { line=1 & col=328 } at respond (/usr/share/opensearch-dashboards/node_modules/elasticsearch/src/lib/transport.js:349:15) at checkRespForFailure (/usr/share/opensearch-dashboards/node_modules/elasticsearch/src/lib/transport.js:306:7) at HttpConnector. (/usr/share/opensearch-dashboards/node_modules/elasticsearch/src/lib/connectors/http.js:173:7) at IncomingMessage.wrapper (/usr/share/opensearch-dashboards/node_modules/lodash/lodash.js:4991:19) at IncomingMessage.emit (node:events:525:35) at IncomingMessage.emit (node:domain:489:12) at endReadableNT (node:internal/streams/readable:1359:12) at processTicksAndRejections (node:internal/process/task_queues:82:21) { status: 400, displayName: 'BadRequest', path: '/otel-v1-apm-span-*/_search', query: { size: 0 }, body: { error: { root_cause: [Array], type: 'x_content_parse_exception', reason: '[1:328] [bool] failed to parse field [must]', caused_by: [Object] }, status: 400 }, statusCode: 400, response: '{"error":{"root_cause":[{"type":"parsing_exception","reason":"[term] query does not support [dispatchConfig]","line":1,"col":328}],"type":"x_content_parse_exception","reason":"[1:328] [bool] failed to parse field [must]","caused_by":{"type":"parsing_exception","reason":"[term] query does not support [dispatchConfig]","line":1,"col":328}},"status":400}', toString: [Function (anonymous)], toJSON: [Function (anonymous)]
}
/*********** I expected to see : some data on this page If applicable, add screenshots to help explain your problem. Environment (please complete the following information): - OS: [e.g. Ubuntu 20.04 LTS] - Version [e.g. 22] Additional context
Add any other context about the problem here. My Environment is Windows 10 and i disabled security features in configurations. I attached all releated files as zip file.
files.zip
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure from examples/jaeger-hotrod by opening the OpenSearch Dashboards observability-traces page, selecting Data-Prepper, and refreshing. Inspect the opensearch-dashboards container output and the attached files.zip, focusing on the trace analytics query that rejects dispatchConfig. Done means the page loads trace data without the x_content_parse_exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100