Operations Staff Offboarding Handover Checklist

Overview

This example uses a Zabbix-responsible employee’s departure as the scenario. In practice, this is a universal checklist — you can replace Zabbix with any business system, any operations tool, or any other scenario.

To ensure a smooth transition of the Zabbix monitoring system, the following is a prioritized checklist of core tasks and materials that the departing employee must hand over:

1. Basic Access Permission Handover

1. Account Inventory
   • Zabbix Web console administrator account
   • SNMP/Agent accounts for monitored servers
   • Database (e.g., MySQL/PostgreSQL) read/write permissions
   • Associated LDAP/AD integration accounts (if applicable)
2. SSH/Remote Access Permissions
   • SSH keys or passwords for Zabbix Server/Proxy
   • Jump server/VPN access permissions (if applicable)

2. System Configuration Documentation

1. Architecture Topology Diagram
   • Annotate Zabbix Server/Proxy/Agent distribution
   • Network traffic flow and critical monitoring nodes
2. Configuration File Backups
   • Key parameter descriptions for zabbix_server.conf and zabbix_proxy.conf
   • Custom script paths (e.g., AlertScripts/ExternalScripts)
3. Monitoring Templates
   • Exported XML template files (host templates, application sets, monitoring items)
   • Third-party template sources (e.g., GitHub/Gitee links)

3. Key Operational Procedures

1. Daily Task Checklist
   • Monitoring item threshold adjustment frequency (e.g., disk space, CPU alerts)
   • Scheduled maintenance windows (e.g., database Housekeeper cleanup)
2. Alert Handling SOP
   • Alert severity rules (e.g., P0–P3)
   • Notification channels (email/SMS/DingTalk/WeCom configuration)
   • Silence rules (e.g., suppressing alerts during maintenance)
3. Disaster Recovery Guide
   • Zabbix database backup commands and schedules
   • Ansible/Shell scripts for rapid Zabbix Server rebuild

4. Data and Integration

1. Historical Data
   • Database size and retention policies (e.g., trend data 30 days, history data 7 days)
   • Grafana integration configuration (e.g., data source IDs, dashboard JSON)
2. API and Automation
   • Common API call examples (e.g., batch host addition)
   • Automation tools (e.g., Python scripts, Zabbix CLI commands)

5. Verification and Handover Checklist

1. Test Cases
   • Simulate triggering an alert to verify the notification chain
   • Manually add a test host to confirm auto-discovery rules are working
2. Contact List
   • Team contacts who depend on Zabbix data (e.g., operations/development/business departments)
   • Vendor support contacts (e.g., Zabbix official/cloud service providers)

Recommended Handover Timeline

• Reserve at least a 2-week overlap period:
  Week 1: Documentation review + permission transfer
  Week 2: Hands-on practice + issue resolution
• Ensure at least a 1-month handover period

By following the steps above, you can minimize handover risks. If time is tight, prioritize handing over permissions, configuration files, and alert procedures.