Mike Perham

Sounds like the optimal solution is to migrate to redis-rb 5.x and then you can opt into hiredis and/or TLS if you want.

I suspect you might be right; it's possible this is a coercion issue. I tried to fix a bunch of lint warnings and might have broke something in doing so....

Inspeqtor reads the SwapFree and SwapTotal attributes in /proc/meminfo. ```go free := memMetrics["SwapFree"] total := memMetrics["SwapTotal"] if free == 0 { hs.Save("swap", "", 100) } else if free == total...

~~~I think one source of confusion: "swap" means "swap available". So 100% means 100% of your swap is available. Machines without swap should never trigger the low swap alert.~~~

Wait, that's backwards. "swap" means "swap in use" and so your rule should trigger. If you don't have swap, you should remove the swap rule.

I see what you are saying. Hmm. I'd recommend swap on every machine along with an alert if you ever use it. The alternative is the Linux OOM handler killing...

Why are you using Inspeqtor if you aren’t using alerts? > On Jun 21, 2018, at 23:29, Shubham Shukla wrote: > > I don't want to send any alerts as...

Set up an inbox filter. Inspeqtor is designed to alert, there’s no way to disable them. > On Jun 22, 2018, at 00:02, Shubham Shukla wrote: > > We are...

And I would be perfectly ok with this being opt-in: `JSON.generate(..., type_smuggling: true)`

AFAICT this PR also fixes a major bug: the cron parser skips the "fallback" hour of DST because the `next` method jumps from "00:59:00 PDT" to "01:00:00 PST" as it...