phaedrusthegreek/transform_vis

Transform Visualization for Kibana

transform_vis's Issues

Can one perform queries on multiple indices with this plugin?

I would like to create visualizations using data from different indices. Is that possible directly or do I need to use jquery and perform ajax calls? Thanks for the super useful plugin.

Is there anyway to have user input with this plugin?

Possibility of using style-tags

Hey,
first let me thank you for the awesome plugin.

Is there a possibility to use CSS for styling the template? A symple <style> tag is not working properly.

Thanks

6.4.0 No index pattern

I see, you just updated to 6.4.0 a few days ago and didn't tag it yet..

when I download and install commit e4b62ff in version 6.4.0 I am not able to save the index pattern. All index patterns are showing correctly in the dropdown-menu but as far as I choose one the visualization window says "No Index Pattern". Same message for all already existing transform-visualizations.

Any suggestions?

Kibana 5.4.1

Any plans to make a release for Kibana 5.4.1?

can we import third js lib in this plugin

can we import third js lib in this plugin, such as highcharts and so on

upgrade transform-vis for kibana 6.8.0

Hello,

Can you upgrade this plugin to kibana 6.8.0

thinks

Update to 6.1.2

Please update to 6.1.2

can this plugin have a pagination?

can this plugin have a pagination for on data?

Support for Kibana 5.6.2

This plugin would help in the development of our kibana dashboard in many ways and currently we're using version 5.6.2 and we cannot downgrade our system due to other plugin incompatibility. We would truly appreciate if you could help us and share if you have plans on supporting latest releases of Kibana (specifically 5.6.2). Thank you so much in advance!

Regards,
Keeshia

Please update the great plugin to 7.*

Hi,
it will be perfect, when you try to upgrade your plugin. We use them in very many vis.
I try it, but now i have a problem with the appstate.
It will be perfect.
Thanks
Classic

Index Pattern Incorrect

Hi guys I have builded this plugin for kibana 5.6 version, but when I'm trying to get it work, I can see that the index patterns are showing as id's and not by their names, and when I'm trying to execute it I'm getting an Elasticsearch error. Also the javascript section is not showing

Can not see JS input window

HI,

After installation of plugin, the JS minput window is not visible, could you please assist?

Thanks,
Jan

Can we pass the output of the query/ JS/ template to an existing visual

Can we pass the output of the query/ JS/ template to an existing visual. Since we don't want to recreate all the existing visuals embedded as html/JS in Template section. Since I am not well versed in JS, please forgive if its a stupid question.

P.S
Thank you so much for the widget/ help you are providing.

Error with 6.4.2

When I change the package.json to 6.4.2 and try to install via git clone, direct file install, or url get this error:

/opt/bitnami/kibana# bin/kibana-plugin install https://github.com/PhaedrusTheGreek/transform_vis/releases/download/6.4.0/transform_vis-6.4.0.zip

Attempting to transfer from https://github.com/PhaedrusTheGreek/transform_vis/releases/download/6.4.0/transform_vis-6.4.0.zip
Transferring 39811 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Error: end of central directory record signature not found
    at /opt/bitnami/kibana/node_modules/yauzl/index.js:179:14
    at /opt/bitnami/kibana/node_modules/yauzl/index.js:539:5
    at /opt/bitnami/kibana/node_modules/fd-slicer/index.js:32:7
    at FSReqWrap.wrapper [as oncomplete] (fs.js:658:17)
Plugin installation was unsuccessful due to error "Error retrieving metadata from plugin archive"

Any suggestions?

How about a plan for Kibana 6.0.0 ?

Thank you so much for this awesome plugin.

It's really helpful for our team in many use cases. We are testing Kibana 6.0.0 rc and would like to upgrade our Kibana from 5.x to 6.0.0 right after an official release.
We'd appreciate it if you could share a plan for 6.0.0 or 6.x.

Bug with importing third party JS

When I import some custom JS libraries, I get the error in the picture I attached. I can't seem to make it go away and it seems like Kibana is trying to load the script before the library is loaded which is causing this error. Any way to get around this? It isn't a nice error to pop up and it happens everytime I sign in.

I get the error when I use either of the following two in the javascript box:

    import_funnelLib: function() {
    $.getScript("https://canvasjs.com/assets/script/jquery.canvasjs.min.js", function( data, textStatus, jqxhr ) {
        console.log("Import Complete");
    });   
 }

or

 before_render: function(){
    $.getScript("https://canvasjs.com/assets/script/jquery.canvasjs.min.js", function( data, textStatus, jqxhr ) {
        console.log("Import Complete");
    });  
 }

And then further down in the javascript box I have:
after_render: function() { $("#chartContainer").CanvasJSChart(options);}
I think this is where the error is

Any idea what I can do?

@PhaedrusTheGreek

Is there a way to access the object returned by function in Javascript box directly inside <script> tag in Template section

@PhaedrusTheGreek... Is there a way to access the object returned by function in Javascript box directly inside <script> tag in Template section. We need the response returned from ES query to be used as an data source for d3 charts used in the Template section. Any thoughts?

Transform_vis_6.0.0 support for Kibana 6.0.1

Hi,
Will Transform_vis_6.0.0 will be supported for Kibana version 6.0.1?

Thanks,
Jan

Plugin not supporting in Kibana version 6.2.3

I tried installing the plugin in 6.2.3 version but i am not able to install it. Is there any branch for 6.2.3 ?

revision up to support kibana 7.x version

Hi,
would you like to take some time to continue working on this plugin to support the latest Kibana version 7.x?
it would be highly appreciated if you can make it happen!
thanks!

Support multiple index queries

It would be nice to do several queries from different indexes.
Just remove Index Pattern dropdown and place it into Query DSL field. For example:

{
  "query_1": { "index-pattern": "index1-*", ... query body ... },
  "query_2": { "index-pattern": "index2-*", ... query body ... }
}

And then use response.query_1... and response.query_2...

I can do pull request for this functionality if you OK with conception.