# Unable to browse another index pattern

**URL:** https://discuss.elastic.co/t/unable-to-browse-another-index-pattern/33924
**Category:** Kibana
**Created:** [November 5, 2015, 8:26pm UTC](https://discuss.elastic.co/t/unable-to-browse-another-index-pattern/33924 "2015-11-05T20:26:13Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![erikstephens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/erikstephens/32/5430_2.png) [@erikstephens](https://discuss.elastic.co/u/erikstephens)
#### Post date: [November 5, 2015, 8:26pm UTC](https://discuss.elastic.co/t/unable-to-browse-another-index-pattern/33924/1 "2015-11-05T20:26:14Z")

</div>

Documents have been indexed and I see the index-pattern in elasticsearch via a direct search to the .kibana index. When in Discover, I keep seeing "loading default index pattern" in the web console/debugger regardless of the index pattern I select. I verified that the index pattern's timestamp field (@timestamp) is present in my events. [This line](https://github.com/elastic/kibana/blob/76ee5abfcff80a5007a4bf794d3d8ce53a22a2a9/src/ui/public/index_patterns/routeSetup/loadDefault.js#L39) is the closest I've come to debugging. How it's getting there when I choose another index pattern is beyond my skills. Perhaps not a kibana issue...

One difference between the documents in this index pattern is they are indexed directly to elasticsearch instead of going through logstash, so maybe not a kibana issue. The @timestamp's look valid when querying elasticsearch directly. The mapping for @timestamp is:

```auto
"@timestamp" : {
    "type" : "date",
    "format" : "strict_date_optional_time||epoch_millis"
 }

```

Fields are showing as indexed in the index pattern settings. Any ideas on what else I should check? This is elasticsearch 2.0 and kibana 4.2.

---

<div class="post-metadata">

### Author: ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)
#### Post date: [November 7, 2015, 8:23pm UTC](https://discuss.elastic.co/t/unable-to-browse-another-index-pattern/33924/2 "2015-11-07T20:23:19Z")

</div>

Curious - Did you ever resolve the issue? It shouldn't matter whether data is loaded through LS or directly into ES.

---

<div class="post-metadata">

### Author: ![erikstephens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/erikstephens/32/5430_2.png) [@erikstephens](https://discuss.elastic.co/u/erikstephens)
#### Post date: [November 9, 2015, 7:30pm UTC](https://discuss.elastic.co/t/unable-to-browse-another-index-pattern/33924/3 "2015-11-09T19:30:29Z")

</div>

Thanks for following up. I just now figured out what I did wrong: the query\_string filter was failing because I disabled `_all` and did not specify an `index.query.default_field`.

---

<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: [July 6, 2017, 2:09pm UTC](https://discuss.elastic.co/t/unable-to-browse-another-index-pattern/33924/4 "2017-07-06T14:09:27Z")

</div>


