Export Documents as CSV

[dennismphil]

Is there any way to CSV export the results on Discover tab in Kibana 4 Beta 2?

Edit 6 Sep 2018: CSV reporting is available for free in X-Pack starting in version 6.0.0. Starting with 6.3.0, CSV reporting is available in the default distribution of Kibana. For 5.3-5.6, @fbaligand maintains a community plugin and comments on this issue when it is updated.

[rashidkpc]

Currently there is no way to export doc results as CSV, this is something we want to implement on the backend so we can return more results than would be reasonable in javascript.

[dennismphil]

Much wanted feature. Looking forward to it

[ZeAleks]

+1

[abdalians]

+1

[ikazoy]

+1

[AlexB030]

Then what is the meaning of the Export-Button when in the Discover-Panel? There is a button, that is not doing anything atm. Or am I misinterpreting its meaning?

[AlexIoannides]

+1

[snasirca]

+1. In order for our support team to be able to use Kibana fully, we need the ability to export a subset of documents (the search results) to CSV.

[damageco]

+1 This functionnality is a much wanted feature for our users too.

[srgshames]

+1

[ZeAleks]

It is now working with the last beta ...

[damageco]

@ZeAleks No, in last beta it's just the export of synthesis results, not the documents.

[Stefan129]

+1 Please add this function...

[dcinzona]

+1

[rashidkpc]

Now that the server is nodeJS based it should be fairly simple to add a route with a size parameter that loads a savedSearch object and exports its results to CSV

[ignaciovazquez]

+1

[Funbit]

+1

[zaakiy]

+1

[ajrasch]

+1

[dc-afinnell]

It seems all visualizations EXCEPT the Table has export.

[gerlachry]

+1

[luzili]

+1

[mooreniemi]

+1

[dvdklnr]

+1

[roman-parkhunovskyi]

+1

[mazing80]

+1

[rashidkpc]

Need a limit warning

[zaakiy]

@rashidkpc

dont mind a warning, but please bear in mind the use case of having to extract approx 360,000 documents.

if that is too much, then at least provide us an easy way to access the json query so that i can construct the query using the gui and then use the json to directly export out of elasticsearch. note that this means i have to do my own json to csv conversion though, which is why i prefer thatyou can implement a way to do large csv exports.

[harbinger55]

+1 This is all I am missing to deploy this into production

[wjimenez5271]

+1

[Ginja]

+1

[missnebun]

+1

[aallegret]

+1 Our teams badly need this particular feature

[lmazuel]

+1

[edouardKaiser]

+1

[wjimenez5271]

FWIW, I created a work-around to enable my end users to export data from a web UI: https://github.com/wjimenez5271/elasticsearch-web-export. Its very crude and by no means a replacement for this feature, but might get you by in the meantime.

[flintbd]

+1

[jim-hendrick]

seriously - the ability to export datasets (warn if you must for large result sets) is really needed the options is what? To manually write ES queries, including authentication (where it exists) and pull the documents by hand? IMHO - the workflow should be something like 1) filter, query, rinse-repeat until you get the results you want 2) select export and whether to only export the currently shown fields, or the entire "row" 3) pick the export format (csv is absolutely fine in most cases, but the ability to select a delimiter or "delimiter set" would be useful where odd characters are included in the data

[LYY]

+1

[nico01f]

+1

[chrisddom]

+1

[dcinzona]

+1 for @jim-hendrick #2

[RoopendraV]

+1

[appasahebs]

yup plz do that. +1

[derikss]

+1

[maharg101]

+1 our use case includes exports of up to 10k results, with selectable fields, so reflecting the table layout would be perfect, thanks :+1:

[ami-navon]

+1

[damikem]

+1

[crudbug]

:+1:

[jdve]

PR #3756 adds this feature. Not fully polished, but maybe a starting point?