# GUID is not a configured index pattern ID Showing the default index pattern

**URL:** <https://discuss.elastic.co/t/guid-is-not-a-configured-index-pattern-id-showing-the-default-index-pattern/217405>\
**Category:** Logs\
**Created:** [January 31, 2020, 3:03pm UTC](https://discuss.elastic.co/t/guid-is-not-a-configured-index-pattern-id-showing-the-default-index-pattern/217405 "2020-01-31T15:03:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![daz1761](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daz1761/32/61856_2.png) [@daz1761](https://discuss.elastic.co/u/daz1761)\
**Post date:** [January 31, 2020, 3:03pm UTC](https://discuss.elastic.co/t/guid-is-not-a-configured-index-pattern-id-showing-the-default-index-pattern/217405/1 "2020-01-31T15:03:47Z")

</div>

I am new to ELK, and I have just spun up the containers including Filebeat via Docker Compose to read some dummy logs from a file (see [https://github.com/moryachok/elasticstack-lab](https://github.com/moryachok/elasticstack-lab)).

When I go to the Discovery tab in Kibana (Firefox for Mac) after creating an index pattern, I get a notification pop up:

"cba24e50-4422-11ea-87a6-196047a921ba" is not a configured index pattern ID  
Showing the default index pattern: "sample-\*" (7ce7e210-442d-11ea-b280-431f48906f3f)

Though all seems to be working, I was wondering why this is happening?

Funnily enough I have someone who did the same process on a Linux machine and didn't get the warning. Is this some browser caching issue?

---

<div class="post-metadata">

**Author:** ![afgomez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/afgomez/32/59274_2.png) [@afgomez](https://discuss.elastic.co/u/afgomez)\
**Post date:** [January 31, 2020, 3:58pm UTC](https://discuss.elastic.co/t/guid-is-not-a-configured-index-pattern-id-showing-the-default-index-pattern/217405/2 "2020-01-31T15:58:55Z")

</div>

Hi @daz1761, welcome to the community!

Did you made it to the discovery page through an external link? It's possible that the ID you mention is present in the URL (look for `index:cba24e50-4422-...` in there) and that's why you are getting the notification.

If you open the discovery page from the sidebar, do you get the same notification?

---

<div class="post-metadata">

**Author:** ![daz1761](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/daz1761/32/61856_2.png) [@daz1761](https://discuss.elastic.co/u/daz1761)\
**Post date:** [January 31, 2020, 4:06pm UTC](https://discuss.elastic.co/t/guid-is-not-a-configured-index-pattern-id-showing-the-default-index-pattern/217405/3 "2020-01-31T16:06:54Z")

</div>

Hi @afgomez yes I've been opening the Discovery from the side bar after a new install (i.e. spinning up all the containers and creating the index pattern) and I get the notification every time.

Yes I've heard that people have had this issue with "bookmarked" pages but I am not doing that so thought I would mention it. Maybe its Firefox doing some form of caching perhaps

---

<div class="post-metadata">

**Author:** ![afgomez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/afgomez/32/59274_2.png) [@afgomez](https://discuss.elastic.co/u/afgomez)\
**Post date:** [February 3, 2020, 8:28am UTC](https://discuss.elastic.co/t/guid-is-not-a-configured-index-pattern-id-showing-the-default-index-pattern/217405/4 "2020-02-03T08:28:58Z")

</div>

> Maybe its Firefox doing some form of caching perhaps

Does it happens with other browsers in your machine?

If not, maybe something went wrong when creating the index pattern. Try deleting it and creating it again and see if that fixes it.

---

<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:** [March 2, 2020, 8:29am UTC](https://discuss.elastic.co/t/guid-is-not-a-configured-index-pattern-id-showing-the-default-index-pattern/217405/5 "2020-03-02T08:29:01Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
