# File Name in Kibana Report in 6.4.1

**URL:** <https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022>\
**Category:** Kibana\
**Created:** [October 4, 2018, 10:12am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022 "2018-10-04T10:12:18Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![sanek64](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sanek64](https://discuss.elastic.co/u/sanek64)\
**Post date:** [October 4, 2018, 10:12am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/1 "2018-10-04T10:12:18Z")

</div>

Hi all,

I faced with a problem that was discussed in the following topic:

> [@File Name in Kibana Report](https://discuss.elastic.co/t/file-name-in-kibana-report/124131):
>
> Hi friends In these moments when we generate a report from Kibana and we export it to CSV we obtain a file with a name with this format or similar "jequmsq202rkd7699226sij5" My query is. Is it possible to specify the name and extension of this report in the kibana configuration? I have reviewed the configuration options of kibana and I do not see anything. Thanks in advance Best regards

Any news about this in 6.4.1 or may be feature request that could be monitored? It is very important for us to add .csv extension to file name for our business partners.

Thanks

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [October 4, 2018, 10:55am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/2 "2018-10-04T10:55:51Z")

</div>

Hello,

The report is currently exported with .csv in the name and the name of the saved object. I tested it just now on Kibana 6.4.0. Are you seeing different results?

---

<div class="post-metadata">

**Author:** ![sanek64](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sanek64](https://discuss.elastic.co/u/sanek64)\
**Post date:** [October 4, 2018, 12:12pm UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/3 "2018-10-04T12:12:27Z")

</div>

Something strange.  
I set up ELK 6.4.1 on my local computer with windows archive and have .csv extension reporting as you said. But when i upgraded my ELK from 6.2.1 to 6.4.1 on Red Hat work stand with rpm package instalation i have not got .csv extension reporting and my file names are trash.  
What other details could i provide you to help me with these strange things?

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [October 4, 2018, 1:48pm UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/4 "2018-10-04T13:48:12Z")

</div>

6.4.2 to 6.4.1? Do you mean maybe 5.4.2?

---

<div class="post-metadata">

**Author:** ![sanek64](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sanek64](https://discuss.elastic.co/u/sanek64)\
**Post date:** [October 4, 2018, 1:49pm UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/5 "2018-10-04T13:49:07Z")

</div>

Sorry, 6.2.1 to 6.4.1

---

<div class="post-metadata">

**Author:** ![sanek64](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sanek64](https://discuss.elastic.co/u/sanek64)\
**Post date:** [October 4, 2018, 3:51pm UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/6 "2018-10-04T15:51:22Z")

</div>

I experemented with my 6.4.1 Kibana version after uprade and found out that new searches, that was saved after upgrading could be reported as .csv extension, but my old discovers that was created on 6.2.1 version are reported in no csv extension and with bad file names.  
Is this a bug or i somehow could reupdate my discovers?

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [October 5, 2018, 2:13pm UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/7 "2018-10-05T14:13:58Z")

</div>

That sounds like a bug, i'll investigate it as it seems weird. In the meantime maybe export and re-importing them could fix it.

---

<div class="post-metadata">

**Author:** ![sanek64](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sanek64](https://discuss.elastic.co/u/sanek64)\
**Post date:** [October 9, 2018, 5:01pm UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/8 "2018-10-09T17:01:40Z")

</div>

Hi Marius,

Any news on this bug?

I've tried to change versions in my dashboard template to 6.4.1, but this does not help.  
Also, i've tried to compare json of my bad exported discovers and those that are exported well and there are no discrepancies at all between them.  
By the way, i am using import-dashboard api to import my objects to servers, maybe it is important here. That's why I dont want to reexport-import my objects now, because i will need to change them after export for import to import-dashboard-api format.

So, any help wil be appreciated.

---

<div class="post-metadata">

**Author:** ![sanek64](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sanek64](https://discuss.elastic.co/u/sanek64)\
**Post date:** [October 10, 2018, 8:47am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/9 "2018-10-10T08:47:47Z")

</div>

Export and manual re-import is also not solving the problem ☹

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [October 10, 2018, 9:24am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/10 "2018-10-10T09:24:04Z")

</div>

I tried it locally now and it seems to be able to generate reports OK after upgrading. The only ones with the old name and no csv extension are the ones that were already generated in version 6.2.1.  
I did this:

1. created a saved search in 6.2.1 and generated a report on it = random name + no csv extension
2. upgraded to 6.4.1 and created a new saved search + generated a report on it = good name + csv extension.
3. generated a report on the old saved search = good name + csv extension.

Is this different from your experience?

---

<div class="post-metadata">

**Author:** ![sanek64](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sanek64](https://discuss.elastic.co/u/sanek64)\
**Post date:** [October 10, 2018, 10:12am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/11 "2018-10-10T10:12:10Z")

</div>

Hi @Marius_Dragomir, thanks for the answer  
Yea, step 3 is different for me. old saved searches after upgrading are still generating bad name + bad extension report. I have tried to manually export-reimport them or change version inside template, but it does not help.

---

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [October 10, 2018, 10:22am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/12 "2018-10-10T10:22:19Z")

</div>

Is there any saved search that has problems that you could upload here? I would like to try importing it in my local instance and check it.  
If not, we could try and look in the verbose logs.  
Add `logging.verbose: true` in kibana.yml, restart kibana, generate a CSV report on a good saved search, then one on a bad saved search and the upload the kibana log here.

---

<div class="post-metadata">

**Author:** ![sanek64](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sanek64](https://discuss.elastic.co/u/sanek64)\
**Post date:** [October 10, 2018, 11:51am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/13 "2018-10-10T11:51:15Z")

</div>

[badTest](https://quickfileshare.org/1iTN/badTest.txt)  
[goodTest](https://quickfileshare.org/1iTO/goodTest.txt)

Ok, @Marius_Dragomir. I add logging.verbose and those are my kibana log. bad Test and good test correspond respectively to bad naming and good naming examples.

---

<div class="post-metadata">

**Author:** ![sanek64](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@sanek64](https://discuss.elastic.co/u/sanek64)\
**Post date:** [October 16, 2018, 10:02am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/14 "2018-10-16T10:02:37Z")

</div>

Hi, @Marius_Dragomir.  
Do my examples help you to solve my problem?

---

<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:** [November 13, 2018, 10:02am UTC](https://discuss.elastic.co/t/file-name-in-kibana-report-in-6-4-1/151022/15 "2018-11-13T10:02:39Z")

</div>

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