# Monitor: Best solutions for keeping track of uptime?

**URL:** <https://meta.discourse.org/t/monitor-best-solutions-for-keeping-track-of-uptime/13807>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [17 במרץ,‏ 2014,‏ 4:36pm UTC](https://meta.discourse.org/t/monitor-best-solutions-for-keeping-track-of-uptime/13807 "2014-03-17T16:36:06Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![justin\_gordon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justin_gordon/32/105029_2.png) [@justin\_gordon](https://meta.discourse.org/u/justin_gordon)\
**Post date:** [23 בנובמבר,‏ 2019,‏ 3:19am UTC](https://meta.discourse.org/t/monitor-best-solutions-for-keeping-track-of-uptime/13807/3 "2019-11-23T03:19:46Z")

</div>

I just signed up for [https://uptimerobot.com/](https://uptimerobot.com/).

I’d like to get the latest recommendations from the Discourse dev team. @sam?

I thought about this today as I discovered that my programming site [https://forum.shakacode.com](https://forum.shakacode.com) was not responding. Yikes! Logging into the server and restarting the container

This is all I needed to get the site back up:

```plaintext
cd /var/discourse/
./launcher restart app

```

I then did the upgrade:

```plaintext
git pull
./launcher rebuild app

```

One “problem” with discourse is that it’s so easy to keep running that it’s easy to forget how to do maintenance!

---

_[View the full topic](https://meta.discourse.org/t/monitor-best-solutions-for-keeping-track-of-uptime/13807)._
