CPU temp and Deployment status

Hello Elastic Team,

I would to build my own Dashboard in Kibana with specific data. Will i be able to capture the CPU temperature, ingest status and Deployment status data in Elasticsearch and create a Dashboard with this info in Kibana?

Please advice
thank you


There are quite a few options.

Capture the data and sent to Elasticsearch using the Index API. 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

We also have Beats, which are lightweight shippers to Elasticsearch. Metricbeat 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/blog/build-your-own-beat

Thank you for your reply. I have installed pretty much all beats provided by Elastic, but i', not quite sure if the metricbeat provides the CPU temperature. I have Metricbeat installed and running, but i don't have that data.
Another question : I would like to capture Ros logs which is under /home/.ros/logs path. Will i be able to get those logs to Elastic and Kibana thru Filebeat or Logstash? I tried to specify the path in Filebeat.yml, but i still don't see Ros logs in Kibana.

Thank you for support,

Hey @tylersmalley ,

Would you please reply me?

Looks like there is a community beat which does CPU temperature - but I have have little information about it. https://github.com/eskibars/lmsensorsbeat

I found this from the community beats section here: https://www.elastic.co/guide/en/beats/libbeat/current/community-beats.html

If that doesn't work you can use a cronjob to capture the metrics and log to a file, which you can then pickup from Filebeat.

I am not familiar with Ros, but I don't see why you wouldn't be able to ingest those using Filebeat. What does the content of those files look like? Are they structured JSON? Do you have an example? Do you see the data in Elasticsearch? What does your Filebeat configuration look like?

@tylersmalley thank you for your quick reply.
I have already tested the lssensorsbeat, but that does not seem to be working. Yes, i found it from community beat section. Would be nice if your guys could add CPU temp information into metricbeat. It would be very helpful.

Appears there is an open issue for that enhancement you can track here: https://github.com/elastic/beats/issues/11848

@tylersmalley following your advice i have created a script to capture CPU temp to a logfile and i set a cronjob to run that script. I have now a log file under /var/log/temp.log. How do i add this data to Kibana now ? I was thinking on creating CPU temp gauge in KIbana.

Hi Tyler,
I have installed and configured lmsensorsbeat, but having issues loading index template into Kibana. It's rinning in my pc, but i dont see any data in Kibana.
i get this error: ERR Failed to perform any bulk index operations: 406 Not Acceptable
2019/11/14 00:22:49.968508 single.go:78: INFO Error publishing events (retrying): 406 Not Acceptable.

Connection established with ES.

here is the lmsensorsbeat.yml

Elasticsearch as output


hosts: ["Localhost:9200"]

index: "lmsensorbeat-%{+yyyy.MM.dd}"

# A template is used to set the mapping in Elasticsearch
# By default template loading is disabled and no template is loaded.
# These settings can be adjusted to load your own template or overwrite existing ones

  # Template name. By default the template name is lmsensorsbeat.
  name: "lmsensorsbeat"

  # Path to template file
  path: "lmsensorsbeat.template.json"

  # Overwrite existing template
  overwrite: true

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