# Metricbeat CPU percentage between 0 and 1
**URL:** https://discuss.elastic.co/t/metricbeat-cpu-percentage-between-0-and-1/82712
**Category:** Beats
**Tags:** metricbeat
**Created:** [April 18, 2017, 12:36pm UTC](https://discuss.elastic.co/t/metricbeat-cpu-percentage-between-0-and-1/82712 "2017-04-18T12:36:30Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@GogLlundain](https://discuss.elastic.co/u/GogLlundain)
#### Post date: [April 18, 2017, 12:36pm UTC](https://discuss.elastic.co/t/metricbeat-cpu-percentage-between-0-and-1/82712/1 "2017-04-18T12:36:30Z")
Hi there,
Posting data to ElasticSearch via LogStash I get CPU values that range from 0 to 1. In the default template this is a scaled\_float, I haven't changed the template.
When I look at discover or I visualise the data this stat remains a value between 0 and 1, how do I get it to render as a percentage between 0 and 100?
I could do it with TimeLion with a multipler, but shouldn't it figure itself out?
Using v5.3 of all components.
Gog.
---
### Author:  [@rcowart](https://discuss.elastic.co/u/rcowart)
#### Post date: [April 18, 2017, 7:06pm UTC](https://discuss.elastic.co/t/metricbeat-cpu-percentage-between-0-and-1/82712/2 "2017-04-18T19:06:16Z")
In the Kibana Index Pattern edit the Field Format, setting it to percentage.
NOTE: If you load the default dashboards it should do this for you, IIRC.
NOTE2: Changing the field format will not help with Timelion. There you will have to handle it yourself as mention.
Rob
---
### Author:  [@GogLlundain](https://discuss.elastic.co/u/GogLlundain)
#### Post date: [April 19, 2017, 8:21am UTC](https://discuss.elastic.co/t/metricbeat-cpu-percentage-between-0-and-1/82712/3 "2017-04-19T08:21:51Z")
Hi Rob,
Thanks for your time.
We have a daily index e.g. metricbeat-2017.04.19 to holds today's data. If I change the index pattern is it persisted forever?
Gog
---
### Author:  [@rcowart](https://discuss.elastic.co/u/rcowart)
#### Post date: [April 19, 2017, 8:36am UTC](https://discuss.elastic.co/t/metricbeat-cpu-percentage-between-0-and-1/82712/4 "2017-04-19T08:36:40Z")
Yes it is. Your index pattern should be metricbeat-\* which means it applies to any indexes that match that pattern, including your daily indexes.
---
### Author:  [@GogLlundain](https://discuss.elastic.co/u/GogLlundain)
#### Post date: [April 19, 2017, 9:14am UTC](https://discuss.elastic.co/t/metricbeat-cpu-percentage-between-0-and-1/82712/5 "2017-04-19T09:14:25Z")
Awesome, that's what I thought.
So what does the logstash template achieve, is is just about how the data is stored and not a hint about how to index/render it?
---
### Author:  [@rcowart](https://discuss.elastic.co/u/rcowart)
#### Post date: [April 19, 2017, 9:27am UTC](https://discuss.elastic.co/t/metricbeat-cpu-percentage-between-0-and-1/82712/6 "2017-04-19T09:27:35Z")
Yes... the index template tells Elasticsearch how to create the index. Kibana uses that information as a starting point for an index pattern, but the patterns can be further modified.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 17, 2017, 9:41am UTC](https://discuss.elastic.co/t/metricbeat-cpu-percentage-between-0-and-1/82712/7 "2017-05-17T09:41:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.