# Discover: view limited fields -\> export: all used fields

**URL:** <https://discuss.elastic.co/t/discover-view-limited-fields-export-all-used-fields/196289>\
**Category:** Kibana\
**Created:** [August 22, 2019, 9:52am UTC](https://discuss.elastic.co/t/discover-view-limited-fields-export-all-used-fields/196289 "2019-08-22T09:52:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![asp](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@asp](https://discuss.elastic.co/u/asp)\
**Post date:** [August 22, 2019, 9:52am UTC](https://discuss.elastic.co/t/discover-view-limited-fields-export-all-used-fields/196289/1 "2019-08-22T09:52:56Z")

</div>

Hi,

we want to use elastic stack to aggregate logs and to filter easily for errors and corresponding stack traces. We also want to combine multiple log files, that we can trace the function calls by the logs.  
Target is to give the ops or tester an easy to use tool (kibana) and then he / she can export the data (stacktraces, etc.) to ship them to the developers.

So in our use case, the ops or tester need to see columns like username, sessionid, requestid, status, etc to filter for the . The developer needs to get all filled / used fields.

I noticed the following:

- when one or more columns are selected for a search, **ONLY these selected columns** are exported.
- when no column is selected, it defaults to \_source field which exports **ALL** fields.

So, is there any better way to than the following workflow?

- load predefined search (loading needed fields)
- set query and filters to shrink resultset to the events which are needed
- remove all columns
- save query as new query (so I will keep my template / preset search)
- generate the csv reporting
- delete search

Or is there a way to create a report for a search when from a dashboard, where it is embedded?

I am hoping to find something like a one or two click workflow for generating the export.

Thanks, Andreas

---

<div class="post-metadata">

**Author:** ![nickpeihl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickpeihl/32/112622_2.png) [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)\
**Post date:** [August 22, 2019, 4:10pm UTC](https://discuss.elastic.co/t/discover-view-limited-fields-export-all-used-fields/196289/2 "2019-08-22T16:10:20Z")

</div>

Please let me know if I'm misunderstanding the question.

As an example, my `filebeat-*` index pattern has nearly 1000 fields. But only the fields that contain data are shown in Discover when no columns are selected. And only those fields are exported in the CSV.

Are you seeing fields in Discover that contain no data? Which version of Kibana are you using?

---

<div class="post-metadata">

**Author:** ![asp](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@asp](https://discuss.elastic.co/u/asp)\
**Post date:** [August 23, 2019, 5:59am UTC](https://discuss.elastic.co/t/discover-view-limited-fields-export-all-used-fields/196289/3 "2019-08-23T05:59:42Z")

</div>

Hi @nickpeihl,

I think you got me wrong.  
When ops or a tester has the task to gather relevant log data, they will use sth. like these columns to identify the needed events (just as example):

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/3/43b47b4a693a258da2e4ea3a9c75e8aa706cfa6b.png)

But the developer is not just interested in these fields, they need additional fields like reqest number, requestBody, responseBody, stackTrace. Maybe dev needs 20 more columns / fields to analyte the issue.

When exporting to csv in discovery:

- if fields / columns are defined -\> only these are exported
- if **no** fields / columns are defined, all **used** columns are exported.

I am searching for an option to export **all used fields** although some fields are selected.

I am using kibana 7.3.0

---

<div class="post-metadata">

**Author:** ![nickpeihl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickpeihl/32/112622_2.png) [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)\
**Post date:** [August 23, 2019, 8:11pm UTC](https://discuss.elastic.co/t/discover-view-limited-fields-export-all-used-fields/196289/4 "2019-08-23T20:11:37Z")

</div>

Thanks for clarifying. What you are asking does not seem possible at this time.

You may want to make your case for a feature request in the Kibana repo. [https://github.com/elastic/kibana/issues/new/choose](https://github.com/elastic/kibana/issues/new/choose)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 20, 2019, 8:11pm UTC](https://discuss.elastic.co/t/discover-view-limited-fields-export-all-used-fields/196289/5 "2019-09-20T20:11:37Z")

</div>

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