Nelson Chan

Did you check the pm2 logs after the server is started? Does it say `INFO: Listening on 3001`?

Interesting. I guess an easy solution would be to add a checkbox to hide a monitor when you add them to the status page.

This is a database timeout error. Looks like it was trying to calculate the uptime, which is a read-heavy operation. Did you check that the disk usage is high, or...

If that's the data structure you want, you would probably do this: ```js for (const tag of monitor.tags) { this.monitorLabelValues[tag.name] = tag.value } ```

Currently we use the ORM in a very raw way, meaning that table joins have to be done manually. You can check `monitor.js:52` for how this is done. But it...

Should probably rebase on master first, #1136 should have fixed the duplicate metrics issue, but I'm guessing it still doesn't handle editing tags correctly.

I guess a really dumb way would be to define a route in the server ```js .get('/basepath', function (req, res, next) { if (req.accepts("html")) { res.send(process.env.basepath); ... ``` and then...

FYI since the `tcp-ping` library and node.js's `Socket.connect()` does not support the use of proxies, this would not be very easy. We may have to switch to another library like...

The `tcp-ping` package uses node.js's `Socket.connect()`, which uses node.js's `dns.lookup()`, which then goes to the system's resolver through `libuv`. The layers of indirection probably increased latency. On the other hand,...

Since the webhook notification sends the entire `monitor` object, anyone (not that I think there are many, if at all) depending on those fields will be affected. Honestly I'm for...