Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

search_phase_execution_exception: [parse_exception] Reason: failed to parse date field in Kibana logs #120144

Closed
bhavyarm opened this issue Dec 1, 2021 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@bhavyarm
Copy link
Contributor

bhavyarm commented Dec 1, 2021

Kibana version: 7.16.0 snapshot Dec 1st

Elasticsearch version: 7.16.0 snapshot Dec 1st

Server OS version: darwin_x86_64

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from staging

Describe the bug: Found while testing the fix #119504 for this bug - #119444

Lens viz displays alright -
Screen Shot 2021-12-01 at 12 57 59 PM

But there is error logs about failed to parse date field [2021-10-27T04:38:34.120Z] with format [epoch_millis] in kibana logs:


log   [11:22:18.174] [info][lens][plugins] Field existence check failed on 75041e60-52c2-11ec-bdbf-a3f2bde16eb0: search_phase_execution_exception: [parse_exception] Reason: failed to parse date field [2021-12-01T16:07:17.742Z] with format [epoch_millis]: [failed to parse date field [2021-12-01T16:07:17.742Z] with format [epoch_millis]]
  log   [11:22:18.175] [error][http] ResponseError: search_phase_execution_exception: [parse_exception] Reason: failed to parse date field [2021-12-01T16:07:17.742Z] with format [epoch_millis]: [failed to parse date field [2021-12-01T16:07:17.742Z] with format [epoch_millis]]
    at onBody (/Users/bhavyarajumandya/Desktop/7.16_snapshot_upgrade/No_error_upgrade/kibana-7.16.0-SNAPSHOT-darwin-x86_64/node_modules/@elastic/elasticsearch/lib/Transport.js:367:23)
    at IncomingMessage.onEnd (/Users/bhavyarajumandya/Desktop/7.16_snapshot_upgrade/No_error_upgrade/kibana-7.16.0-SNAPSHOT-darwin-x86_64/node_modules/@elastic/elasticsearch/lib/Transport.js:291:11)
    at IncomingMessage.emit (node:events:402:35)
    at endReadableNT (node:internal/streams/readable:1343:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  meta: {
    body: { error: [Object], status: 400 },
    statusCode: 400,
    headers: {
      'x-opaque-id': 'd87eb419-e556-46ab-920a-f2413176921d',
      'x-elastic-product': 'Elasticsearch',
      'content-type': 'application/json; charset=UTF-8',
      'content-length': '877'
    },
    meta: {
      context: null,
      request: [Object],
      name: 'elasticsearch-js',
      connection: [Object],
      attempts: 0,
      aborted: false
    }
  }
}
@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Dec 1, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

@flash1293
Copy link
Contributor

Dupe of #119445 - this will be fixed in 8.0

Great job spotting this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

3 participants