# Need server/system serial number output in kibana dashboard **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-monitoring\ **Created:** [June 27, 2020, 1:09pm UTC](https://discuss.elastic.co/t/need-server-system-serial-number-output-in-kibana-dashboard/238949 "2020-06-27T13:09:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![D\_ELK](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@D\_ELK](https://discuss.elastic.co/u/D_ELK)\ **Post date:** [June 27, 2020, 1:09pm UTC](https://discuss.elastic.co/t/need-server-system-serial-number-output-in-kibana-dashboard/238949/1 "2020-06-27T13:09:22Z")
Hi, I have build my ELK stack on local machine (ELK version- 6.8.10) . In order to get more details like machine/server serial number, I have added few entries in filebeat.yml file. After adding few lines under add\_host\_metadata section, I took restart of filebeat service and post that service is successfully up and running fine. But I am not able to view serial\_number field in my kibana dashboard (after discovering filebeat index). Also there is one field in filebeat output which is "host.id" , I have no idea that what information is this ?? I have already crossed checked my instance and serial number with host.id output , unfortunately it is not matching with any of the outputs. Please have a look on below filebeat.yml file and share further suggestion to resolve this issue ASAP. 🙂 '''' [root@XXXXX~]# cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID\_LIKE="rhel fedora" VERSION\_ID="7" PRETTY\_NAME="CentOS Linux 7 (Core)" ANSI\_COLOR="0;31" CPE\_NAME="cpe:/o:centos:centos:7" HOME\_URL="[https://www.centos.org/](https://www.centos.org/)" BUG\_REPORT\_URL="[https://bugs.centos.org/](https://bugs.centos.org/)" [root@XXXXX ~]# systemctl status filebeat.service -l ● filebeat.service - Filebeat sends log files to Logstash or directly to Elasticsearch. Loaded: loaded (/usr/lib/systemd/system/filebeat.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2020-06-27 12:36:32 UTC; 27min ago Docs: [https://www.elastic.co/products/beats/filebeat](https://www.elastic.co/products/beats/filebeat) Main PID: 49249 (filebeat) CGroup: /system.slice/filebeat.service └─49249 /usr/share/filebeat/bin/filebeat -c /etc/filebeat/filebeat.yml -path.home /usr/share/filebeat -path.config /etc/filebeat -path.data /var/lib/filebeat -path.logs /var/log/filebeat Jun 27 12:36:32 XXXX systemd[1]: Started Filebeat sends log files to Logstash or directly to Elasticsearch.. [root@XXXX ~]# [root@xxxxxx ~]# cat /etc/filebeat/filebeat.yml ###################### Filebeat Configuration Example ######################### # This file is an example configuration file highlighting only the most common # options. The filebeat.reference.yml file from the same directory contains all the # supported options with more comments. You can use it as a reference. # # You can find the full configuration reference here: # [https://www.elastic.co/guide/en/beats/filebeat/index.html](https://www.elastic.co/guide/en/beats/filebeat/index.html) # For more available modules and options, please see the filebeat.reference.yml sample # configuration file. #=========================== Filebeat inputs ============================= filebeat.inputs: # Each - is an input. Most options can be set at the input level, so # you can use different inputs for various configurations. # Below are the input specific configurations. - type: log #============================= Filebeat modules =============================== filebeat.config.modules: # Glob pattern for configuration loading path: ${path.config}/modules.d/\*.yml # Set to true to enable config reloading reload.enabled: false # Period on which files under path should be checked for changes #reload.period: 10s #==================== Elasticsearch template setting ========================== setup.template.settings: index.number\_of\_shards: 3 #index.codec: best\_compression #\_source.enabled: false #================================ General ===================================== # The name of the shipper that publishes the network data. It can be used to group # all the transactions sent by a single shipper in the web interface. #name: # The tags of the shipper are included in their own field with each # transaction published. #tags: ["service-X", "web-tier"] # Optional fields that you can specify to add additional information to the # output. #fields: # env: staging #============================== Dashboards ===================================== # These settings control loading the sample dashboards to the Kibana index. Loading # the dashboards is disabled by default and can be enabled either by setting the # options here, or by using the `-setup` CLI flag or the `setup` command. #setup.dashboards.enabled: false # The URL from where to download the dashboards archive. By default this URL # has a value which is computed based on the Beat name and version. For released # versions, this URL points to the dashboard archive on the [artifacts.elastic.co](http://artifacts.elastic.co) # website. #setup.dashboards.url: #============================== Kibana ===================================== # Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API. # This requires a Kibana endpoint configuration. setup.kibana: # Kibana Host # Scheme and port can be left out and will be set to the default (http and 5601) # In case you specify and additional path, the scheme is required: [http://localhost:5601/path](http://localhost:5601/path) # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601 host: "localhost:5601" # Kibana Space ID # ID of the Kibana Space into which the dashboards should be loaded. By default, # the Default Space will be used. #space.id: #============================= Elastic Cloud ================================== # These settings simplify using filebeat with the Elastic Cloud ([https://cloud.elastic.co/](https://cloud.elastic.co/)). # The cloud.id setting overwrites the `output.elasticsearch.hosts` and # `setup.kibana.host` options. # You can find the `cloud.id` in the Elastic Cloud web UI. #cloud.id: # The cloud.auth setting overwrites the `output.elasticsearch.username` and # `output.elasticsearch.password` settings. The format is `:`. #cloud.auth: #================================ Outputs ===================================== # Configure what output to use when sending the data collected by the beat. #-------------------------- Elasticsearch output ------------------------------ #output.elasticsearch: # Array of hosts to connect to. # hosts: ["localhost:9200"] # Enabled ilm (beta) to use index lifecycle management instead daily indices. #ilm.enabled: false # Optional protocol and basic auth credentials. #protocol: "https" #username: "elastic" #password: "changeme" #----------------------------- Logstash output -------------------------------- output.logstash: # The Logstash hosts hosts: ["localhost:5044"] # Optional SSL. By default is off. # List of root certificates for HTTPS server verifications #ssl.certificate\_authorities: ["/etc/pki/root/ca.pem"] # Certificate for SSL client authentication #ssl.certificate: "/etc/pki/client/cert.pem" # Client Certificate Key #ssl.key: "/etc/pki/client/cert.key" #================================ Processors ===================================== # Configure processors to enhance or manipulate events generated by the beat. processors: - add\_host\_metadata: server\_details: name: xxxxxx serial\_number: 0000-0009-3938-xxx-3444-06 - add\_cloud\_metadata: ~ #================================ Logging ===================================== # Sets log level. The default log level is info. # Available log levels are: error, warning, info, debug #logging.level: debug # At debug level, you can selectively enable logging only for some components. # To enable all selectors use ["\*"]. Examples of other selectors are "beat", # "publish", "service". #logging.selectors: ["\*"] #============================== Xpack Monitoring =============================== # filebeat can export internal metrics to a central Elasticsearch monitoring # cluster. This requires xpack monitoring to be enabled in Elasticsearch. The # reporting is disabled by default. # Set to true to enable the monitoring reporter. #xpack.monitoring.enabled: false # Uncomment to send the metrics to Elasticsearch. Most settings from the # Elasticsearch output are accepted here as well. Any setting that is not set is # automatically inherited from the Elasticsearch output configuration, so if you # have the Elasticsearch output configured, you can simply uncomment the # following line. #xpack.monitoring.elasticsearch: [root@xxxxxx ~]# '''' ---
**Author:** ![D\_ELK](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@D\_ELK](https://discuss.elastic.co/u/D_ELK)\ **Post date:** [June 28, 2020, 10:00am UTC](https://discuss.elastic.co/t/need-server-system-serial-number-output-in-kibana-dashboard/238949/2 "2020-06-28T10:00:46Z")
Hi, Can anybody please check my post and share further comments. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 28, 2020, 10:53am UTC](https://discuss.elastic.co/t/need-server-system-serial-number-output-in-kibana-dashboard/238949/3 "2020-06-28T10:53:54Z")
Please format your code, logs or configuration files using `` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and not the citation button. It will make your post more readable. Or use markdown style like: ```` ``` CODE ``` ```` This is the icon to use if you are not using markdown format: ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e6e239431ec2d71cbf1beef741f2e93e7cc762c.jpg) There's a live preview panel for exactly this reasons. Lots of people read these forums, and many of them will simply skip over a post that is difficult to read, because it's just too large an investment of their time to try and follow a wall of badly formatted text. If your goal is to get an answer to your questions, it's in your interest to make it as easy to read and understand as possible. Please update your post. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [June 28, 2020, 10:54am UTC](https://discuss.elastic.co/t/need-server-system-serial-number-output-in-kibana-dashboard/238949/4 "2020-06-28T10:54:07Z")
Please be patient in waiting for responses to your question and refrain from pinging multiple times asking for a response or opening multiple topics for the same question. This is a community forum, it may take time for someone to reply to your question. For more information please refer to the [Community Code of Conduct](https://www.elastic.co/community/codeofconduct) specifically the section "Be patient". Also, please refrain from pinging folks directly, this is a forum and anyone that participates might be able to assist you. If you are in need of a service with an SLA that covers response times for questions then you may want to consider talking to us about a [subscription](https://www.elastic.co/subscriptions). It's fine to answer on your own thread after 2 or 3 days (not including weekends) if you don't have an answer. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 26, 2020, 10:54am UTC](https://discuss.elastic.co/t/need-server-system-serial-number-output-in-kibana-dashboard/238949/5 "2020-07-26T10:54:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.