Kibana version 6.0

[byn017]

Hi,

The plugin doesn't work with kibana version 6.0.
Does the plugin going to support version 6.0?

Thanks

[nreese]

The current plugin does not currently support 6.0.

[byn017]

Is it going to support version 6.0? If yes when do you think it will be ready?

Thanks in advance

[nreese]

It may eventually but not a huge priority so I would not expect it any time in the next three months.

[Shifter2600]

Thx for the update @nreese

[spreeker]

Are the changes big?

[Pilarbr82]

Hi!!!!

I would like to use the plugin. When do you think it would be ready??

Thanks a lot

[nreese]

I have not been able to look into updating the plugin to 6.0. I have no estimation on when the plugin will get updated. Pull requests are welcome

[Pilarbr82]

Ok, thank you for your quickly answer

[pranshu1995]

Hey @nreese Is the plugin compatible for Kibana 6 now?

[nreese]

no

[alexandrejuma]

Would be great to have the plugin working for Kibana 6.

[pranshu1995]

Hey All

I've tried to migrate the plugin to Kibana v6.1.2.
But I am facing some issues.
The visualisation is loading without any errors.
But the problem is that data is not being plotted on the map.
I checked the query being sent in Dev-Tools and the data fetched is fine.
Here is my fork : https://github.com/pranshu1995/enhanced_tilemap

Any help would be appreciated.
Thank you

[swathigorijala]

It would be better if have this plugin for 6+

[cspielmann]

this plugin is so good in 5.X.
I am eager to get it for 6.X as I just migrated....

[JacobBrandt]

Unfortunately, you probably won't see this plugin work again for newer versions without getting your hands dirty and figuring out all the Kibana API changes made between 5 and 6. Fair warning, if you haven't been doing Kibana development at all then it's a lot to wrap your head around. The Kibana team has even completely removed functionality that this plugin was dependent on in versions of 6 which means you'll have to rework some of the code for certain features to work.

If you want this plugin to work then you'll most likely have to get your hands dirty in which I have this to say...write a new plugin or rewrite the plugin. If you plan to be brave and work on a kibana plugin then keep these things in mind.

• Don't have any code outside of the controller/provider that is directly dependent on Kibana.
• Don't have any code be dependent on how Kibana parses the ES response. Come up with your own data structure and pass it along.
• Keep your Kibana dependent code to a minimum.

I realize that all three of these in a way are related and that's the point. It's very important to keep your plugin isolated from the Kibana code as it's too volatile.

If you do these three things then upgrading will be a heck of a lot easier and all your upgrade changes to new versions will be isolated to the two files that are dependent on the Kibana API and it's services (courier, app state, indexPatterns, etc.). Once you resolve the Kibana dependency issues in your controller and provider than you'll know everything else will just work as it's just your own code from before.