# CPU temp and Deployment status

**URL:** <https://discuss.elastic.co/t/cpu-temp-and-deployment-status/206659>\
**Category:** Kibana\
**Created:** [November 5, 2019, 6:31pm UTC](https://discuss.elastic.co/t/cpu-temp-and-deployment-status/206659 "2019-11-05T18:31:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [November 7, 2019, 3:37pm UTC](https://discuss.elastic.co/t/cpu-temp-and-deployment-status/206659/2 "2019-11-07T15:37:51Z")

</div>

Absolutely!

There are quite a few options.

Capture the data and sent to Elasticsearch using the [Index API](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-index_.html). You will probably want to first create the mapping for this data to describe to Elasticsearch how you would like it to be indexed. [https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping.html)

We also have Beats, which are lightweight shippers to Elasticsearch. [Metricbeat](https://www.elastic.co/guide/en/beats/metricbeat/current/index.html) might have the information you want to capture, with the added benefit they ship with some dashboards to get you started. Since the beats do the heavy lifting of handling the ES connection, retries, etc. Sometimes it makes sense to build your own Beat [https://www.elastic.co/guide/en/beats/devguide/7.x/new-beat.html](https://www.elastic.co/guide/en/beats/devguide/7.x/new-beat.html) [https://www.elastic.co/blog/build-your-own-beat](https://www.elastic.co/blog/build-your-own-beat)

---

_[View the full topic](https://discuss.elastic.co/t/cpu-temp-and-deployment-status/206659)._