SudevPK
(Sudev P K)
June 4, 2019, 6:55am
1
I have created one index pattern.but the created index pattern is not visible.
2 Likes
Hi, I have the same issue for 7.1.0 version
3 Likes
alchy
(Alchy)
June 7, 2019, 1:55pm
3
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.
1 Like
I have created an another topic ...
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)
June 11, 2019, 8:09pm
5
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)
June 12, 2019, 7:13pm
6
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)
July 4, 2019, 4:28am
7
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
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 :
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.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 :
opened 11:29AM - 02 Jul 19 UTC
closed 10:35AM - 16 Jul 19 UTC
bug
Team:Core
Feature:Saved Objects
**Kibana version:** 7.1.1
**Elasticsearch version:** 7.1.1
**Original inst… all method (e.g. download page, yum, from source, etc.):**
Install from scratch with yum, generic configuration, 100% automatic.
Cluster ES 3 nodes
**Describe the bug:**
Kibana seems to have an issue on it's index .kibana at creation :
When trying to access the Saved Object, Kibana return 400 Bad Request error, and Elasticsearch throw FieldData error on .kibana index
I can create and find my index-pattern using the API, but Kibana isn't able to find them as it's search request got the FieldData exception.
**NOTE** : This issue seems a bit random, it happen on one out of the three clusters I created today (since we are in 7+), all created the same way with scripts.
**NOTE** : I found a post on the elastic forums where 6+ people seems to have the same behavior since 7+
https://discuss.elastic.co/t/kibana-7-cant-load-index-pattern/180167
I'll create more clusters tomorrow to observe more the frequency of this issue.
**Provide logs and/or server output (if relevant):**
Elastic log when I refresh the Saved Objects page :
```
[2019-07-02T11:08:48,327][DEBUG][o.e.a.s.TransportSearchAction] [elastic01] [.kibana][0],
node[RmpqDbnZTMmmrGTVe5sOZA], [R], s[STARTED], a[id=UOCFUQwpREy44aF76avXfw]:
Failed to execute [SearchRequest{searchType=QUERY_THEN_FETCH, indices=[.kibana],
indicesOptions=IndicesOptions[ignore_unavailable=false,
...
Caused by: java.lang.IllegalArgumentException: Fielddata is disabled on text fields by default.
Set fielddata=true on [type] in order to load fielddata in memory by uninverting the inverted
index. Note that this can however use significant memory. Alternatively use a keyword field
instead.
```
Index-pattern present in the saved object and curl GET work, but Kibana can't find it as it get hit by the FieldData error
`curl -X GET "http://localhost:5601/api/saved_objects/index-pattern/filebeat-ulf" -H 'kbn-xsrf: true'`
`{"id":"filebeat-ulf","type":"index-pattern","updated_at":"2019-07-02T11:07:17.553Z","version":"WzUsMV0=","attributes":{"title":"filebeat-7.1.1-ulf-*","timeFieldName":"@timestamp"},"references":[],"migrationVersion":{"index-pattern":"6.5.0"}}`
neef
(Paul de Neef)
July 4, 2019, 11:28pm
9
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.
system
(system)
Closed
August 1, 2019, 11:33pm
10
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.