Someone pointed out in comments on the blog post (https://about.gitlab.com/2019/08/27/tyranny-of-the-clock/#co...) that systemd actually has some good functionality for that.
As others have said here, autoscaling has gotchas. I won't recount those reasons, but there are two other relevant points: 1) Check out the graph in the 'An illuminating graph' section. The connection rate spikes by a…
Oh, that's a fun story. We use https://github.com/google/mtail to turn log data into metrics exported for prometheus. We were already doing this for our haproxy logs; we just added a stanza to capture a secondary…
We definitely take deliberate effort to dis-incentivize blame; it's specifically called out in our values at https://about.gitlab.com/handbook/values/#blameless-problem-... but speaking as an employee, I can confirm…
Someone pointed out in comments on the blog post (https://about.gitlab.com/2019/08/27/tyranny-of-the-clock/#co...) that systemd actually has some good functionality for that.
As others have said here, autoscaling has gotchas. I won't recount those reasons, but there are two other relevant points: 1) Check out the graph in the 'An illuminating graph' section. The connection rate spikes by a…
Oh, that's a fun story. We use https://github.com/google/mtail to turn log data into metrics exported for prometheus. We were already doing this for our haproxy logs; we just added a stanza to capture a secondary…
We definitely take deliberate effort to dis-incentivize blame; it's specifically called out in our values at https://about.gitlab.com/handbook/values/#blameless-problem-... but speaking as an employee, I can confirm…