Yes, this works fine.
Except :
â Obersvability-> Applications â Logs Events:
Thereâs also a security issue in the background. But I donât know, if this belongs together âŚ
And on the console of the dashboards, I could see this:
PPL query fetch err: StatusCodeError: Bad Request
at respond (E:\Apps\opensearch-dashboards\node_modules\elasticsearch\src\lib\transport.js:349:15)
at checkRespForFailure (E:\Apps\opensearch-dashboards\node_modules\elasticsearch\src\lib\transport.js:306:7)
at HttpConnector. (E:\Apps\opensearch-dashboards\node_modules\elasticsearch\src\lib\connectors\http.js:173:7)
at IncomingMessage.wrapper (E:\Apps\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: â/_plugins/_pplâ,
query: {},
body: â{\nâ +
â âerrorâ: {\nâ +
â âreasonâ: âInvalid Queryâ,\nâ + "details": "can't resolve Symbol(namespace=FIELD_NAME, name=patterns_field) in type env",\n +
â âtypeâ: âSemanticCheckExceptionâ\nâ +
â },\nâ +
â âstatusâ: 400\nâ +
â}â,
statusCode: 400,
response: â{\nâ +
â âerrorâ: {\nâ +
â âreasonâ: âInvalid Queryâ,\nâ + "details": "can't resolve Symbol(namespace=FIELD_NAME, name=patterns_field) in type env",\n +
â âtypeâ: âSemanticCheckExceptionâ\nâ +
â },\nâ +
â âstatusâ: 400\nâ +
â}â,
toString: [Function (anonymous)],
toJSON: [Function (anonymous)]
}
Iâm not sure, if this are different topics, or if this belongs togehterâŚ
For my feeling, thereâs something wrong in the communicationâŚ
Perhaps a fault in the yml-configs ?
The certificates are looking good. Thereâs no error or something insecure in the browser.
unfortunately, I didnât fix this.
But I also hadnât time to spend for this topic.
Perhaps, after the summer-break I could work on it or use another solution âŚ