Timelion: no values in time series breaks .fit function



I want to visualize data of different sources in timelion.
Some sources have events each seconds, some are only generating data each 5 minutes.
If I set the interval in timelion to 1 minute, I will not get a line for data which is gathered each 5 minutes. So I used .fit(nearest) and everything is fine


I have no data in the time series, because the log producer failed for example.
Then timelion is thowing following exception:

Timelion: Error: in cell #4: Cannot read property '1' of undefined

 Less Info
Error:  in cell #4: Cannot read property '1' of undefined
    at throwWithCell (/data/elk/kibana/kibana-5.1.2-linux-x86_64/src/core_plugins/timelion/server/handlers/chain_runner.js:30:11)
    at /data/elk/kibana/kibana-5.1.2-linux-x86_64/src/core_plugins/timelion/server/handlers/chain_runner.js:192:11
    at bound (domain.js:280:14)
    at runBound (domain.js:293:12)
    at tryCatcher (/data/elk/kibana/kibana-5.1.2-linux-x86_64/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (/data/elk/kibana/kibana-5.1.2-linux-x86_64/node_modules/bluebird/js/main/promise.js:503:31)
    at Promise._settlePromiseAt (/data/elk/kibana/kibana-5.1.2-linux-x86_64/node_modules/bluebird/js/main/promise.js:577:18)
    at Promise._settlePromises (/data/elk/kibana/kibana-5.1.2-linux-x86_64/node_modules/bluebird/js/main/promise.js:693:14)
    at Async._drainQueue (/data/elk/kibana/kibana-5.1.2-linux-x86_64/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (/data/elk/kibana/kibana-5.1.2-linux-x86_64/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues (/data/elk/kibana/kibana-5.1.2-linux-x86_64/node_modules/bluebird/js/main/async.js:15:14)
    at runCallback (timers.js:637:20)
    at tryOnImmediate (timers.js:610:5)
    at processImmediate [as _immediateCallback] (timers.js:582:5)

Any workaround available here?

Using Kibana 5.1.2

Thanks, Andreas

(Felix Stürmer) #2

Hi @asp,

this problem is being tracked on Github as #10236. A workaround has been suggested in one of the comments.

(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.