# Different .kibana\_\* indices After upgrading **URL:** \ **Category:** Kibana\ **Created:** [November 23, 2021, 7:15am UTC](https://discuss.elastic.co/t/different-kibana-indices-after-upgrading/289912 "2021-11-23T07:15:57Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)\ **Post date:** [November 23, 2021, 7:15am UTC](https://discuss.elastic.co/t/different-kibana-indices-after-upgrading/289912/1 "2021-11-23T07:15:57Z")
Upgrade ELK stack from 7.13 to 7.15 I checked _/\_cat/indices/.kibana_?v\* ```auto health status index uuid pri rep docs.count docs.deleted store.size pri.store.size green open .kibana-event-log-7.15.2-000001 6TDXTgf8RwGjVH3LMJcOCA 1 1 57 0 195.2kb 97.5kb green open .kibana-event-log-7.12.0-000004 jCatWqqqRJmUplxQ1hgD9w 1 1 0 0 416b 208b green open .kibana-event-log-7.12.0-000005 U76-rUAARaGC_DfcCpRu6Q 1 1 0 0 416b 208b green open .kibana_security_session_1 IAslrfK5Sc6AcFbAoyu_3g 1 1 1 0 11kb 5.5kb green open .kibana-event-log-7.12.0-000006 amxJywUMSPib_-J0ExE6nA 1 1 0 0 416b 208b green open .kibana_7.12.0_001 o5xRcvxgSsSztBNOCfIkJA 1 1 889 76 5.6mb 2.8mb green open .kibana-event-log-7.12.0-000003 tqJa5UroT_qVl3yQuyAIEg 1 1 0 0 416b 208b green open .kibana_task_manager_7.15.2_001 DGlfNTB8RIWdGErmzWWVfg 1 1 34 1994 733.9kb 331.7kb green open .kibana_7.13.2_001 MBCEN4KvSrW4WUmNXLAvHw 1 1 1841 490 8.3mb 4mb green open .kibana-event-log-7.13.2-000002 9AzRupr4RRSOHvGQI2ESWA 1 1 11555241 0 1.3gb 671.2mb green open .kibana-event-log-7.13.2-000003 j-1akr2xRpCcMevd4DTi6A 1 1 12541998 0 1.4gb 720.2mb green open .kibana-event-log-7.13.2-000004 4nUblHNZTuW09FrpyhIBoA 1 1 1031364 0 130.3mb 65.1mb green open .kibana-event-log-7.13.2-000005 cgOKFRa5SAWYXoGPfv8Eaw 1 1 702537 0 86.7mb 43.4mb green open .kibana_task_manager_7.13.2_001 TByrB3fUSTSfQnf1v5aGpQ 1 1 29 2144 650.1kb 381.1kb green open .kibana_7.15.2_001 D2FpFf09Skq0Ww6rxvp6Bg 1 1 1848 2766 19.5mb 9.7mb ``` which `.kibana` index i can delete safely without intrupting and dashboards or it can be deleted automatically. ---
**Author:** ![Marco\_Liberati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marco_liberati/32/82953_2.png) [@Marco\_Liberati](https://discuss.elastic.co/u/Marco_Liberati)\ **Post date:** [November 23, 2021, 1:37pm UTC](https://discuss.elastic.co/t/different-kibana-indices-after-upgrading/289912/2 "2021-11-23T13:37:14Z")
Hi @Aniket_Pant , you can have a look at this page to know more about kibana indices, why there are kept and it which case you can delete them safely: [Upgrade migrations | Kibana Guide [7.15] | Elastic](https://www.elastic.co/guide/en/kibana/7.15/upgrade-migrations.html#upgrade-migrations-old-indices) (and all the sections above for a more in-depth information). ---
**Author:** ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)\ **Post date:** [November 24, 2021, 6:33am UTC](https://discuss.elastic.co/t/different-kibana-indices-after-upgrading/289912/3 "2021-11-24T06:33:49Z")
```auto alias index filter routing.index routing.search is_write_index .kibana .kibana_7.15.2_001 - - - - .kibana_7.15.2 .kibana_7.15.2_001 - - - - .kibana-event-log-7.15.2 .kibana-event-log-7.15.2-000001 - - - true .kibana-event-log-7.12.0 .kibana-event-log-7.12.0-000003 - - - false .kibana-event-log-7.12.0 .kibana-event-log-7.12.0-000004 - - - false .kibana-event-log-7.13.2 .kibana-event-log-7.13.2-000002 - - - false .kibana_task_manager_7.13.2 .kibana_task_manager_7.13.2_001 - - - - .kibana-event-log-7.13.2 .kibana-event-log-7.13.2-000004 - - - false .kibana_7.13.2 .kibana_7.13.2_001 - - - - .kibana-event-log-7.13.2 .kibana-event-log-7.13.2-000003 - - - false .kibana-event-log-7.13.2 .kibana-event-log-7.13.2-000005 - - - true .kibana-event-log-7.12.0 .kibana-event-log-7.12.0-000005 - - - false .kibana_task_manager .kibana_task_manager_7.15.2_001 - - - - .kibana_task_manager_7.15.2 .kibana_task_manager_7.15.2_001 - - - - .kibana-event-log-7.12.0 .kibana-event-log-7.12.0-000006 - - - true ``` [Handling old .kibana\_N indices](https://www.elastic.co/guide/en/kibana/7.15/upgrade-migrations.html#upgrade-migrations-old-indices) > Kibana only uses the index that the `.kibana` and `.kibana_task_manager` alias points to. in my case `.kibana` ,`.kibana_7.15.2` alias is pointing to `.kibana_7.15.2_001` and `.kibana_7.15.2_001` respectively but their `is_write_index` is `-` `.kibana_task_manager` , `.kibana_task_manager_7.15.2` is pointing to ` .kibana_task_manager_7.15.2_001` their also `is_write_index` is `-` can i delete it `.kibana_7.13.2` index `.kibana_event-log-7.13.2` index and `.kibana-event-log-7.12.0` ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 24, 2021, 8:51pm UTC](https://discuss.elastic.co/t/different-kibana-indices-after-upgrading/289912/4 "2021-11-24T20:51:54Z")
@Marco_Liberati can users just delete older versions of indices completely. eg if they are on 7.15, anything with a version number lower than than in the name can just be removed? ---
**Author:** ![Marco\_Liberati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marco_liberati/32/82953_2.png) [@Marco\_Liberati](https://discuss.elastic.co/u/Marco_Liberati)\ **Post date:** [November 29, 2021, 9:42am UTC](https://discuss.elastic.co/t/different-kibana-indices-after-upgrading/289912/5 "2021-11-29T09:42:30Z")
From the info provided `.kibana` is pointing to the newer version, therefore you can delete older `.kibana_7.13`/`.kibana_7.12` indexes. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 27, 2021, 9:42am UTC](https://discuss.elastic.co/t/different-kibana-indices-after-upgrading/289912/6 "2021-12-27T09:42:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.