Created Index Pattern is not visible in KIbana 7.0.1

[SudevPK]

I have created one index pattern.but the created index pattern is not visible.

[Benjamin_Carriou]

Hi, I have the same issue for 7.1.0 version

[alchy]

I've the exact same issue with 7.1. The create index patten wizzard for Kibana seems not to be working. I would gladly provide any output from Elastic if you ask for it.

[Benjamin_Carriou]

I have created an another topic ...

I can't create indexes patterns with ECK

Hello everyone, I just freshly installed an Elastic stack on Kubernetes in following tutorial: https://www.elastic.co/guide/en/cloud-on-k8s/current/index.html So I have an elasticsearch cluster of two nodes (test phase;)) + an instance of Kibana that connects to it. Everything seems to work because everything is in a "green" state: Elasticsearch kubectl get elasticsearch NAME HEALTH NODES VERSION PHASE AGE cloud green 2 7.1.0 Operational 4h Kibana …

[afuggetta (Andrea Fuggetta)]

Any solution here?

I have the same issue, the wizard seems as though it creates the index-pattern. But when I click on discover, it asks for the index pattern to be created.

So at this point I can't visualize my data.

[afuggetta (Andrea Fuggetta)]

Hey @Alex_Piggott, any ideas here?
I recreated the cluster and tried different indices but nothing is working.
I upgraded to the latest 7.1.1, it seems like this issue started after the 7.0 upgrade.

Is there a ticket opened for this?

[neef (Paul de Neef)]

Same issue here. After clean install and loading documents with logstash the index itself exists.

yellow open agw_production_xps_agw-xps-xps_sfc203343 582xQ3MbSBmfWOkUejiLSw 1 1 266440 12664 143.1mb 143.1mb

Go into Discover and Kibana asks to create index pattern. Create the index pattern and make it favorite. The pattern name does not appear under the [Create index pattern] button. Go back to discover and Kibana asks to create an index pattern again.

The index exists but it looks like Kibana fails to save the index pattern.

POST .kibana/_search
{
"query": {
"term": {
"type": {
"value": "index-pattern"
}
}
}
}

{
"took" : 1,
"timed_out" : false,
"_shards" : {
"total" : 1,
"successful" : 1,
"skipped" : 0,
"failed" : 0
},
"hits" : {
"total" : {
"value" : 0,
"relation" : "eq"
},
"max_score" : null,
"hits" :
}
}

Stack:
elasticsearch-7.1.0-1.x86_64
kibana-7.1.1-1.x86_64
logstash-7.2.0-1.noarch

[TanguyB]

Hello,

Can you look at the log of your elasticsearch when you try to access the Saved Object (to visualize your index-pattern) ?

And check if you have Fielddata error on the index .kibana

(the index is created but kibana can't perform any search on it)

This seems to be the same case as :

Not possible to create Index patterns in Kibana

I am having issues creating Index patterns in Kibana. When I save the index pattern it first appears in the UI, but as soon as I navigate from the page it disappears. If I query the .kibana index trough the dev tools, I can see that there appears to be a Index pattern created, but Kibana doesn't seem to be able to query it. I belive that this error message is related to the issue, as I see it right after creating the index pattern: kibana: {"type":"response","@timestamp":"2019-06-13T08:40:12Z"…

Kibana 7 can't load index pattern

Kibana: 7.0.1 ES: 7.0.1 When i create index pattern in Kibana, it can load the fields in the indexes. However, when i go to discovery page, it prompts me "In order to visualize and explore data in Kibana, you'll need to create an index pattern to retrieve data from Elasticsearch." I can reload this index pattern by ID like this though: /app/kibana#/management/kibana/index_patterns/83c2bf60-7188-11e9-8feb-fd1dd5f8f608?_g=()&_a=(tab:indexedFields) Any advise?

I created an issue on github on this :

Kibana 7+ can't search saved_objects, FieldData error thrown on .kibana index

[neef (Paul de Neef)]

Thanks,

That will certainly help driving this towards resolution.

After I found similar issues on the forum, I cleaned up everything and got back to a 6.8.1 ELK stack. Therefore I can't do as you suggested nor get the logs.