search

elastic / timelion

Timelion was absorbed into Kibana 5. Don't use this. Time series composer for Elasticsearch and beyond.
Other
347 stars 79 forks source link

Can't seem to specify a different index #156

Closed nlowe closed 8 years ago

nlowe commented 8 years ago

Timelion appears to only be querying against logstash-* indices. In my system, I have a few different indices for different applications. For example, I'm exporting vSphere Performance metrics to an index that has the following pattern: vsphere-yyy-MM-dd. I've tried changing the index parameter (.es(index="vsphere*")) and the default_index option in .../kibana/installedPlugins/timelion/timelion.js and both return zero documents, however I can verify that I do have documents in these indices as I can view them in Kibana's Discover tab.

Furthermore, it appears that the default_index: _all setting is only returning documents from the logstash indices:

image

Is there a config setting I missed, or something I have to do to my indices to get timelion to recognize them?

rashidkpc commented 8 years ago

Pointing at the wrong es? Is it possible that your vsphere indices are using a different timefield? If you change timelion.json you may need to rm -rf optimize/bundles in your Kibana directory. Given that _all is only returning logstash-* docs there is almost certainly a deeper problem in your elasticsearch setup. I'm not able to replicate this behavior.

screen shot 2016-07-19 at 1 40 11 pm
nlowe commented 8 years ago

Ah, I think it was the timestamp field. I thought that was handled in the index mapping, but it must be a kibana thing. Changing the timestamp field in the .es() query now pulls results. Thanks!

rashidkpc commented 8 years ago

Cool, glad you sorted it out. I try to keep my timefield the same in all of my indices, if possible.