Create GitLab network troubleshooting guide
Want to help? Co-assign yourself and ping me!
networking in the issue description is about computer systems on a network (WAN/LAN/VLAN/SDN, or Kubernetes spiderweb) being able to connect to and exchange data with one another.
This covers:
- OSI model: mostly Network layer, maybe a little of Data Link, Transport, and Session layers too
- TCP/IP stack: Internet and Transport layer
but not Application-layer stuff.
Problem:
Networking issues with scaled self-managed GitLab can be tricky to troubleshoot.
Proposal:
Develop resource for troubleshooting networking-specific problems.
Why?
To provide Support team, and ideally customers/users, with guidance on how to debug and troubleshoot common problems related to networking and GitLab at scale.
What?
Content might include:
ping
traceroute
tracepath
telnet
tcpdump
netstat
ss
ip
ngrep
nmap
Possibly expand upon or include additional examples for:
curl
openssl
Results
Intended results are to create a SSoT resource that Support team uses to boost performance indicators (FRT, NRT, CSAT, docs)
Success as part of ticket deflection through documentation can be measured in terms # of times its viewed (google analytics) or linked to (in slack or tickets).
Results would mostly be long-term. The more the resource is linked to, used by others, and iterated upon, the greater the results will be.
Fun/relevant image I found: