# \[SOLVED\] One specific metric stopped working in Timelion **URL:** \ **Category:** Kibana\ **Tags:** timelion\ **Created:** [September 20, 2018, 10:48am UTC](https://discuss.elastic.co/t/solved-one-specific-metric-stopped-working-in-timelion/149275 "2018-09-20T10:48:11Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![peoh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peoh/32/35696_2.png) [@peoh](https://discuss.elastic.co/u/peoh)\ **Post date:** [September 20, 2018, 10:48am UTC](https://discuss.elastic.co/t/solved-one-specific-metric-stopped-working-in-timelion/149275/1 "2018-09-20T10:48:11Z")
Edit: This is in Kibana 6.2.4. Hi! Long time lurker, always seem to solve most issues by reading the forums but this I cannot figure out. So, today when I look at my dashboard in Kibana one of my visuals stopped working. The data is cpu from Metricbeat. The thing is, all other metrics works fine, for example ram-use show up as it should. And the data is present in ES, I can browse and filter them in Discover just fine. They just don't show up in Timelion. About 10 hosts, CPU-Usage: ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/2/320bfc31e332a8fde5a922b11747ef2ef5b9c139.jpeg) Other metrics works fine, this is memory (from the same index): ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/e/eee7d73f34e0f01dc130ecc1ee6bac9a3c2a9adf.png) Data is present in ES: ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/b/2be5432a198eab6377a76bebe445a6ab38059bc2.png) TImelion works fine on other visualizations: ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/3/d32acb0ed571f37f20eb56ddb53bf262dc193cc4.png) But specifically cpu-metric wont show: ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/f/cf58e1d1f5a31a26c3a7ffff15e34d4dcb3d3d6d.png) I did nothing that I know of at 02:00, and at this point I don't even know where to start looking. Any ideas? ---
**Author:** ![peoh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peoh/32/35696_2.png) [@peoh](https://discuss.elastic.co/u/peoh)\ **Post date:** [September 20, 2018, 2:22pm UTC](https://discuss.elastic.co/t/solved-one-specific-metric-stopped-working-in-timelion/149275/2 "2018-09-20T14:22:42Z")
I have now updated to Kibana 6.4.1, however the error remains. ---
**Author:** ![peoh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peoh/32/35696_2.png) [@peoh](https://discuss.elastic.co/u/peoh)\ **Post date:** [September 21, 2018, 6:29am UTC](https://discuss.elastic.co/t/solved-one-specific-metric-stopped-working-in-timelion/149275/3 "2018-09-21T06:29:42Z")
Solved. This was a faulty index. Don't know how but there were some corrupt data making all metrics in that index inaccessable. I have a new index for each day and it stopped working at 00:00 UTC but the timezone-difference made it look likte it happend 02:00. I just deleted that index and everything works fine. Got an upgrade out of it 🙂 ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [September 21, 2018, 8:43pm UTC](https://discuss.elastic.co/t/solved-one-specific-metric-stopped-working-in-timelion/149275/4 "2018-09-21T20:43:58Z")
Nice! Glad to hear it worked out after all. > I have a new index for each day and it stopped working at 00:00 UTC but the timezone-difference made it look likte it happend 02:100: Hm, maybe a faulty change had been made to the index template? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 19, 2018, 8:44pm UTC](https://discuss.elastic.co/t/solved-one-specific-metric-stopped-working-in-timelion/149275/5 "2018-10-19T20:44:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.