GitLab Advanced for System Administrators
This class teaches GitLab for operations in your organization – admin skills, configuration, and maintaining your own GitLab instance as part of the larger IT environment.
This course is customized for your specific deployment of GitLab. It covers advanced monitoring and troubleshooting tasks for a GitLab self-managed instance. This course is not intended for gitlab.com customers.
GitLab Advanced System Administration Training covers some features that are available in all three GitLab pricing tiers (Free, Premium, and Ultimate), some features that are only available in Premium and Ultimate, and a small number of features that are only available in Ultimate.
Available formats for this course
Duration1 day/8 hours of instruction
Public Classroom Pricing
Starting at: $795(USD)
GSA Price: $685
Group Rate: $695
Part 1: Using GitLab CLI Utilities
- GitLab CLI Utilities
- Best Practices for Development
Part 2: Viewing Active Logs
- Information in Active Logs
- Active Logs for Troubleshooting Issues
Part 3: Monitoring Your GitLab Instance
- Health Status
- Server Status
- Disaster Recovery
Part 4: Working with GitLab Support: How to Generate Error Reports
- Unicorn Errors
- Puma Errors
- GitLab 500 Errors
- Sidekiq Errors
- Workhorse Errors
- Rails Console
- API/DB Queries
Part 5: Best Practices for Preventing Integration Problems
- Common Causes
- Common Problems
- Best Practices for Preventing
Part 6: Resolving User and Group Problems
- User Password and Permission Issues
- Group and Project Permission Issues
Attendees should already be familiar at a basic knowledge level with the following concepts:
- GitLab Certified Associate certification or equivalent knowledge.
- GitLab System Administration Basic Training course completion or equivalent knowledge.
Professionals who would benefit from this training include:
- Tier 2 system administrators or support team members for a GitLab self-managed instance responsible for monitoring and troubleshooting at their organization.
- Apply best practices for using CLI Utilities
- Interpret information found in Active Logs and status reports to monitor and troubleshoot issues
- Resolve architecture breaks
- Apply best practices for preventing integration problems
- Resolve user and group problems
- Work with GitLab Support to troubleshoot errors