# Custom index not showing in Kibana V8.8.0 **URL:** \ **Category:** Kibana\ **Created:** [June 21, 2023, 7:36pm UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621 "2023-06-21T19:36:35Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![huzaifa224](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/huzaifa224/32/105868_2.png) [@huzaifa224](https://discuss.elastic.co/u/huzaifa224)\ **Post date:** [June 21, 2023, 7:36pm UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/1 "2023-06-21T19:36:35Z")
I have multiple filebeats v 7.17.5 are configured on different remote servers with custom index names. I have recently updated my ELk stack to 8.8.0 and also updating the filebeat version to 8.8.0. I also try to add some new remote ubuntu servers in elk but the issue is i try to create custom index and start the filebeat but that index is not showing in kibana v8.80 data view. here is the my custom index settings. ```auto output.elasticsearch: # Array of hosts to connect to. hosts: "http://x.x.x.x.x:9200" username: "citsale" password: "mFVKkXXNnOuUzgahLpLpp" # Protocol - either `http` (default) or `https`. ssl.verification_mode: none # Authentication credentials - either API key or username/password. index: "test" setup.template.name: "test" setup.template.pattern: "test-*" ``` ---
**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:** [June 22, 2023, 1:47am UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/2 "2023-06-22T01:47:00Z")
Does it show in `GET _cat/indices?v` ---
**Author:** ![huzaifa224](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/huzaifa224/32/105868_2.png) [@huzaifa224](https://discuss.elastic.co/u/huzaifa224)\ **Post date:** [June 22, 2023, 8:43am UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/3 "2023-06-22T08:43:22Z")
Nops, its not showing in `GET \_cat/indices?v' ---
**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:** [June 26, 2023, 5:54am UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/4 "2023-06-26T05:54:07Z")
Ok then Filebeat isn't sending anything to Elasticsearch. You might need to check the logs of it. ---
**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\ **Post date:** [June 26, 2023, 6:48am UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/5 "2023-06-26T06:48:00Z")
As Mark said, check FB logs and the network communication. If you don't have logs, enable it at least temporary For test purpose, you can see does FB read a log by changing: ```auto output.console: pretty: true ``` ---
**Author:** ![huzaifa224](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/huzaifa224/32/105868_2.png) [@huzaifa224](https://discuss.elastic.co/u/huzaifa224)\ **Post date:** [June 26, 2023, 8:10am UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/6 "2023-06-26T08:10:08Z")
I found some error but didn't know why its occurring i was following the same procedure in FB 7.17.7 to load the template in ELK and that was working, but when i tried to same steps for FB 8.8.0 i am getting the below error. `Exiting: error loading template: failed to put data stream: could not put data stream: 400 Bad Request: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"no matching index template found for data stream [linux]"}],"type":"illegal_argument_exception","reason":"no matching index template found for data stream [linux]"},"status":400}. Response body: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"no matching index template found for data stream [linux]"}],"type":"illegal_argument_exception","reason":"no matching index template found for data stream [linux]"},"status":400}` ---
**Author:** ![huzaifa224](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/huzaifa224/32/105868_2.png) [@huzaifa224](https://discuss.elastic.co/u/huzaifa224)\ **Post date:** [June 26, 2023, 8:11am UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/7 "2023-06-26T08:11:40Z")
i also tried to disable the data stream but no luck. ---
**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\ **Post date:** [June 26, 2023, 8:17am UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/8 "2023-06-26T08:17:21Z")
So you had 7.17.7 and go for FB 8.8.0? Do you have additional modules enabled? It sounds like you have the system module enabled. ---
**Author:** ![huzaifa224](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/huzaifa224/32/105868_2.png) [@huzaifa224](https://discuss.elastic.co/u/huzaifa224)\ **Post date:** [June 26, 2023, 8:20am UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/9 "2023-06-26T08:20:09Z")
Yes, i had using 7.17.7 and then upgraded to 8.8.0. Yes, i have enabled the modules apache nginx, system ---
**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\ **Post date:** [June 26, 2023, 8:41am UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/10 "2023-06-26T08:41:24Z")
The most likely you haven't completed the upgrade process. Follow [the upgrade steps.](https://www.elastic.co/guide/en/beats/libbeat/8.8/upgrading.html) ```auto ./filebeat setup --index-management ./filebeat setup --dashboards ``` If this will not work then `filebeat setup -e`. There is an option to export templates for only 3 modules, and manually create, described [here](https://discuss.elastic.co/t/no-matching-index-template-found-for-data-streamd/307485) , and you will need dashboards, export, import. ---
**Author:** ![huzaifa224](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/huzaifa224/32/105868_2.png) [@huzaifa224](https://discuss.elastic.co/u/huzaifa224)\ **Post date:** [July 1, 2023, 1:08pm UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/11 "2023-07-01T13:08:27Z")
Hi @Rios thanks for the help. I can see the index now in Index Templates, but when i trying to create a DataView to view the logs of filebeat so that index is not showing there ---
**Author:** ![huzaifa224](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/huzaifa224/32/105868_2.png) [@huzaifa224](https://discuss.elastic.co/u/huzaifa224)\ **Post date:** [July 1, 2023, 1:16pm UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/12 "2023-07-01T13:16:50Z")
while running the filebeat setup -e the index loaded in index template but getting the below error. `Exiting: error loading template: failed to put data stream: could not put data stream: 400 Bad Request: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"no matching index template found for data stream [staging]"}],"type":"illegal_argument_exception","reason":"no matching index template found for data stream [staging]"},"status":400}. Response body: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"no matching index template found for data stream [staging]"}],"type":"illegal_argument_exception","reason":"no matching index template found for data stream [staging]"},"status":400}` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 29, 2023, 1:17pm UTC](https://discuss.elastic.co/t/custom-index-not-showing-in-kibana-v8-8-0/336621/13 "2023-07-29T13:17:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.