# Monitoring the hardware **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [March 26, 2018, 6:31am UTC](https://discuss.elastic.co/t/monitoring-the-hardware/125551 "2018-03-26T06:31:53Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mruthyu](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mruthyu](https://discuss.elastic.co/u/mruthyu)\ **Post date:** [March 26, 2018, 6:31am UTC](https://discuss.elastic.co/t/monitoring-the-hardware/125551/1 "2018-03-26T06:31:53Z")
Wanted to know whether the following events were captured in system logs of UNIX and Windows servers so that filebeat can be used to identify them. Disk failure Memory failure Power failure Or is there any better way to handle these events using any other beat other than filebeat. ---
**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\ **Post date:** [March 26, 2018, 3:09pm UTC](https://discuss.elastic.co/t/monitoring-the-hardware/125551/2 "2018-03-26T15:09:32Z")
Monitoring hardware is a broad topic, and it depends on what you want to monitor and how. For example some failures will be reported as failures in log files, and for that you can use filebeat, but other failures will appear as changes in other metrics (as increasing number of errors) that could be obtained by metricbeat or heartbeat. To be notified when some of these events happen, you may take a look to the [alerting features of X-Pack](https://www.elastic.co/products/x-pack/alerting). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 23, 2018, 3:09pm UTC](https://discuss.elastic.co/t/monitoring-the-hardware/125551/3 "2018-04-23T15:09:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.