# System uptime?

**URL:** https://discuss.elastic.co/t/system-uptime/92966
**Category:** Beats
**Tags:** metricbeat
**Created:** [July 13, 2017, 8:47am UTC](https://discuss.elastic.co/t/system-uptime/92966 "2017-07-13T08:47:46Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![TimWard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timward/32/19574_2.png) [@TimWard](https://discuss.elastic.co/u/TimWard)
#### Post date: [July 13, 2017, 8:47am UTC](https://discuss.elastic.co/t/system-uptime/92966/1 "2017-07-13T08:47:46Z")

</div>

I'm looking at replicating the functionality of a legacy monitoring system, and Metricbeat appears to collect most of the data I need, with one thing missing being system uptime. (Which is used to generate alarms if it's not very long, as that suggests the system has rebooted.)

I can get a proxy for that by seeing how long process 1 has been running

processes: ['.\*']

```auto
processors:
- drop_event:
    when:
      and:
      - equals:
          metricset.name: process
      - not:
          equals:
            system.process.pid: 1

```

but this is not very pretty. Is there a better way?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 10, 2017, 8:47am UTC](https://discuss.elastic.co/t/system-uptime/92966/2 "2017-08-10T08:47:48Z")

</div>

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