3 ms·
Documentation also just doesn't cover the kind of issue the GitLab post is talking about. Sure, good docs on what talks to what and so on will help someone lear
by cranekam 4y ago
Documentation also just doesn't cover the kind of issue the GitLab post is talking about. Sure, good docs on what talks to what and so on will help someone learn the lay of the land but it's not going to pinpoint the cause of a spike of 502 errors. Working that kind of thing out requires looking at the problem with a fresh set of eyes to see what's really happening, not what should be happening according to the docs. Some of the best troubleshooters I know figure things out by just looking at what's going on. What's this server talking to? Why is this backend slower? What else is happening on this host? Which network links? etc. None of this is in a manual.
- hericium 4y ago> Documentation also just doesn't cover the kind of issue the GitLab post is talking about. Sure, good docs on what talks to what and so on will help someone learn the lay of the land but it's not going to pinpoint the cause of a spike of 502 errors. And that's perfectly fine. This post was published so GL folks can say "we figured out something tricky/interesting and our scale is what made it more tricky". I love figuring out "Frankenstein" type of bugs, errors and problems myself. What I dislike figuring out is something that shouldn't require any figuring out at all. I read GitLab or Cloudflare's posts with pleasure. These doesn't seem to be written solely as technical recruitment "we do cool stuff" posts.