# Kibana unexpectedly changed timeFieldName

**URL:** <https://discuss.elastic.co/t/kibana-unexpectedly-changed-timefieldname/76946>\
**Category:** Kibana\
**Created:** [March 1, 2017, 8:44am UTC](https://discuss.elastic.co/t/kibana-unexpectedly-changed-timefieldname/76946 "2017-03-01T08:44:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexander](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@Alexander](https://discuss.elastic.co/u/Alexander)\
**Post date:** [March 1, 2017, 8:44am UTC](https://discuss.elastic.co/t/kibana-unexpectedly-changed-timefieldname/76946/1 "2017-03-01T08:44:16Z")

</div>

We've faced with a problem when Kibana unexpectedly changed timeFieldName for a index-pattern. As far as we know no one changed it. But: Was:

```auto
-bash-4.1$ curl "http://localhost:9200/.kibana/index-pattern/logstash-*?pretty"
{
  "_index" : ".kibana",
  "_type" : "index-pattern",
  "_id" : "logstash-*",
  "_version" : 2277,
  "found" : true,
  "_source" : {
    "title" : "logstash-*",
    "timeFieldName" : "@timestamp",
    "fields" : "<some>"
  }
}

```

After some time:

```auto
-bash-4.1$ curl "http://localhost:9200/.kibana/index-pattern/logstash-*?pretty"
{
  "_index" : ".kibana",
  "_type" : "index-pattern",
  "_id" : "logstash-*",
  "_version" : 2283,
  "found" : true,
  "_source" : {
    "title" : "logstash-*",
    "timeFieldName" : "received_at",

```

So the question is - what could cause this changes ? Or how to detect it ?  
Thanks in advice.

---

<div class="post-metadata">

**Author:** ![spalger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spalger/32/14092_2.png) [@spalger](https://discuss.elastic.co/u/spalger)\
**Post date:** [March 1, 2017, 5:21pm UTC](https://discuss.elastic.co/t/kibana-unexpectedly-changed-timefieldname/76946/2 "2017-03-01T17:21:00Z")

</div>

The only way to change the timeFiledName in the Kibana UI is to either; delete the index pattern and recreate it, or create a new index pattern with the same pattern.

Unless you have an application that might be modifying the `.kibana` index outside of Kibana, or some plugins installed that might be doing this, then someone with access to your Kibana must have made this change.

---

<div class="post-metadata">

**Author:** ![Alexander](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@Alexander](https://discuss.elastic.co/u/Alexander)\
**Post date:** [March 1, 2017, 6:23pm UTC](https://discuss.elastic.co/t/kibana-unexpectedly-changed-timefieldname/76946/3 "2017-03-01T18:23:16Z")

</div>

Does Kibana provide any way to catch this changes ? Only verbose logging ?

---

<div class="post-metadata">

**Author:** ![spalger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spalger/32/14092_2.png) [@spalger](https://discuss.elastic.co/u/spalger)\
**Post date:** [March 1, 2017, 7:52pm UTC](https://discuss.elastic.co/t/kibana-unexpectedly-changed-timefieldname/76946/4 "2017-03-01T19:52:45Z")

</div>

It does not, Kibana does not have a centralized location to store the history for objects yet.

---

<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 29, 2017, 7:53pm UTC](https://discuss.elastic.co/t/kibana-unexpectedly-changed-timefieldname/76946/5 "2017-03-29T19:53:00Z")

</div>

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