Prompt Library
1-Click ChatGPT Prompts for Writing Internal Runbooks
Tired of inconsistent or outdated documentation? Use these internal runbook ChatGPT prompts to standardize your operational procedures, from incident response to routine maintenance. Automate runbook creation with ChatBoost and ensure your team has clear, actionable guides for any situation, saving hours of manual writing.
Add ChatBoost to ChromeSave these prompts into ChatBoost and reuse them with Alt+P.
Prompt Library (27)
27 PromptsFree
Draft Incident Triage Steps
Generate the initial steps for a new incident response runbook to ensure rapid assessment.
Outline an incident triage runbook for a '[System Name]' outage to quickly assess impact and escalate. Detail steps for: 1. Initial alert verification. 2. Checking system monitoring dashboards (e.g., [Dashboard Tool]). 3. Defining severity levels (SEV-1, SEV-2, SEV-3). 4. Communication protocol for notifying the on-call engineer and stakeholders.
Database Connection Failure Runbook
Create a detailed runbook for diagnosing and resolving database connection failures.
Draft a runbook for troubleshooting a '[Database Type]' connection failure for the '[Application Name]' service. Include sections for: 1. Verifying network connectivity to the database host. 2. Checking database credentials and connection strings. 3. Inspecting application logs for specific error codes like '[Error Code Example]'. 4. Restarting the application service in the correct order. 5. Escalation path to the DBA team.
Deployment Rollback Procedure
Generate a safe and standardized procedure for rolling back a failed deployment.
Outline a runbook for rolling back a failed deployment of '[Application Name]' in our '[Environment Name]' environment. The deployment tool is '[Deployment Tool]'. Cover: 1. Command to trigger the rollback. 2. Steps to verify the previous version is active. 3. Monitoring application health post-rollback. 4. Communication plan for informing the development team.
High CPU Usage Investigation
Create a diagnostic runbook for investigating unexpected high CPU usage on a server.
Draft a troubleshooting runbook for an alert indicating >90% CPU usage on a '[Operating System]' server running '[Service Name]'. Include commands to: 1. Identify the top CPU-consuming processes (e.g., using 'top' or 'htop'). 2. Check recent application logs for errors. 3. Analyze recent code changes or traffic spikes. 4. Steps for collecting a performance profile if the issue persists.
Post-Incident Report (PIR) Template
Generate a structured template for a post-incident report to facilitate blameless learning.
Design a Post-Incident Report (PIR) or postmortem template. Include these sections: Summary, Timeline of Events (with timestamps), Root Cause Analysis (using the '5 Whys' method), Impact (customer-facing, internal), Resolution Steps, and Action Items (with owners and due dates) to prevent recurrence.
Server Patching Procedure
Outline a standard operating procedure for applying security patches to servers.
Develop a runbook for monthly security patching of our '[Operating System]' servers. Include: 1. Pre-patching checks (backups, system health). 2. Command to apply updates. 3. Post-patching verification steps (reboot, service checks). 4. Rollback procedure in case of failure. 5. Documentation of patching activity in '[Tracking System]'.
Database Backup & Restore Test
Create a runbook for periodically testing the database backup and restoration process.
Outline a runbook for quarterly testing of our '[Database Type]' backup and restore process to verify data integrity. Steps should include: 1. Identifying the latest backup file. 2. Provisioning a temporary, isolated restore environment. 3. Executing the restore command. 4. Running specific data validation queries to confirm success. 5. Decommissioning the temporary environment.
SSL Certificate Renewal
Detail the process for renewing an SSL certificate before it expires.
Detail a runbook for renewing an SSL certificate for the domain '[domain.com]' handled by '[Certificate Authority]' on '[Web Server Software]'. Cover: 1. Generating a new Certificate Signing Request (CSR). 2. Submitting the CSR to the CA. 3. Validating domain ownership. 4. Installing the new certificate on the server. 5. Verifying the new certificate is active.
User Access Request Fulfillment
Standardize the procedure for granting a new user access to a specific system.
Draft a runbook for the IT helpdesk to process a user access request for '[Application Name]', tracked in '[Ticketing System]'. Steps should include: 1. Verifying manager approval. 2. Creating the user account in '[Identity Provider]'. 3. Assigning the user to the correct role/group ('[Role Name]'). 4. Sending a confirmation email to the user and manager. 5. Closing the ticket.
Log Rotation Check
Create a runbook to verify that log rotation is configured and working correctly.
Draft a runbook to periodically check that log rotation is functioning correctly for '[Application Name]' on our '[Operating System]' servers. Include commands to: 1. Locate the log rotation configuration file (e.g., in /etc/logrotate.d/). 2. Verify the configuration settings (rotation frequency, size limits). 3. Check the log directory for archived log files. 4. Manually force a log rotation to test the process.
New Engineer Onboarding Checklist
Generate a runbook that serves as a technical onboarding checklist for new engineers.
Develop a technical onboarding runbook for a new engineer joining the '[Team Name]' team. Include a checklist of tasks: 1. Gaining access to source code repositories (e.g., GitHub). 2. Setting up the local development environment for '[Main Application]'. 3. Obtaining credentials for monitoring tools like '[Monitoring Tool]'. 4. Introduction to the team's CI/CD pipeline. 5. Link to key architectural diagrams.
How to Set Up Local Dev Environment
Create a detailed guide for setting up the local development environment for a specific project.
Outline a runbook detailing the step-by-step process for setting up a local development environment for the '[Project Name]' project. The project uses '[Programming Language]', '[Framework]', and '[Database]'. Include prerequisites (e.g., specific software versions), commands for cloning the repo, installing dependencies, running database migrations, and starting the local server.
Code Deployment Process Overview
Explain the team's code deployment process from commit to production for new members.
Detail our team's code deployment process in a runbook. Start from a developer committing code to the '[branch-name]' branch in Git. Describe the stages: 1. Automated tests run by '[CI Tool]'. 2. Code review process. 3. Merging to the main branch. 4. Automatic deployment to the '[Staging Environment]'. 5. Manual promotion to the '[Production Environment]'.
Standard Runbook Template
Create a standardized template for all new runbooks to ensure consistency.
Generate a markdown template for a standard operational runbook. The template should have the following sections with placeholder text: 'Title', 'Owner', 'Last Updated', 'Purpose', 'Prerequisites', 'Step-by-Step Procedure', 'Verification Steps', 'Rollback Plan', and 'Escalation Contacts'.
Clarify Vague Runbook Steps
Rewrite a section of an existing runbook to be more clear and actionable.
I have a runbook with a vague step. Please rewrite it for clarity and to remove ambiguity. The current step is: 'Check the logs and restart the service if needed.' Rewrite this step to be more specific for an application named '[App Name]' where logs are in '[Log Path]' and the service is managed by 'systemctl'. Include the exact commands to use.
Add a Verification Section
Generate a 'Verification Steps' section for an existing runbook.
I have a runbook for restarting the '[Service Name]' service. I need to add a 'Verification Steps' section to it. Generate 3-4 concrete steps to confirm the service is running correctly after the restart. Include checking the service status, tailing the logs for a successful startup message, and making a test API call to a health check endpoint '[/health]'.
Convert Prose to Checklist
Transform a paragraph-style procedure into a numbered checklist for better readability.
Convert the following paragraph into a clear, numbered checklist runbook format. Paragraph: 'First, you need to SSH into the server. Then, navigate to the application directory. After that, pull the latest changes from the git repository. Finally, you should restart the application server to apply the changes.'
API Endpoint Unresponsive
Create a runbook for troubleshooting an unresponsive API endpoint.
Draft a runbook for diagnosing why the '[/api/endpoint]' endpoint on service '[Service Name]' is returning 503 errors. Include steps to: 1. Check the service's logs for errors related to this endpoint. 2. Verify the health of downstream dependencies (e.g., database, other microservices). 3. Use a tool like 'curl' to make a direct request from the server to rule out network issues. 4. Check resource utilization (CPU, memory) on the service's host.
Emergency Security Patch
Generate a runbook for applying an emergency, out-of-band security patch.
Create a high-urgency runbook for deploying an emergency security patch for vulnerability '[CVE-ID]'. The process must be fast but safe. Include: 1. Communication plan for stakeholders. 2. Steps to apply the patch in a staging environment first. 3. A minimal set of critical tests to run in staging. 4. Procedure for a rolling deployment to production to avoid downtime. 5. Post-deployment monitoring plan.
Firewall Rule Change Request
Outline the procedure for requesting, approving, and implementing a firewall rule change.
Develop a runbook for the process of changing a firewall rule, addressing both the requester and the network administrator. Include sections for: 1. How to submit a request (ticket template with required info: source IP, destination IP, port, protocol, business justification). 2. The approval workflow. 3. The implementation steps for the admin using '[Firewall Vendor]'. 4. Verification process with the requester.
Scaling Up Application Instances
Create a runbook for manually scaling up the number of application instances during high traffic.
Outline a runbook for scaling the '[Application Name]' service from [X] to [Y] instances in our '[Cloud Provider/Platform, e.g., Kubernetes]' environment. Include: 1. The command or UI steps to change the instance count. 2. Monitoring new instances to ensure health. 3. Key performance metrics to watch after scaling (e.g., response time, error rate). 4. Procedure for scaling back down after the traffic spike.
On-Call Handover Procedure
Create a checklist for the handover process between on-call engineers.
Draft a runbook to be used for on-call handover. It should be a checklist for the outgoing engineer to fill out for the incoming engineer. Include points like: 1. Summary of any active or recent incidents. 2. Any ongoing deployments or risky changes. 3. Any systems that are currently in a degraded state. 4. Confirmation that alerts have been successfully routed to the new on-call person.
Generate Mermaid.js Diagram
Create a Mermaid.js flowchart from a set of procedural steps to visualize the runbook.
I have a runbook with the following steps. Convert them into a Mermaid.js flowchart diagram. Steps: 1. Alert fires for high latency. 2. On-call engineer investigates logs. 3. If database query is slow, escalate to DBA. 4. If application error, check recent deployments. 5. If recent deployment, initiate rollback. 6. If no recent deployment, restart service. 7. Resolve incident.
Cache Flushing Procedure
Create a runbook for safely flushing a distributed cache like Redis.
Develop a runbook for flushing the '[Cache Name]' Redis cache used by '[Application Name]'. Emphasize safety to avoid a cache stampede. Include: 1. Scenarios when flushing is appropriate. 2. The exact command to flush the cache (e.g., `redis-cli FLUSHALL`). 3. A warning about potential high load on the primary database after flushing. 4. Steps to monitor database load and application performance immediately after the flush.
Decommissioning a Server
Generate a checklist for safely decommissioning a server from the infrastructure.
Create a runbook checklist for decommissioning a server with hostname '[hostname]'. The process must ensure no service disruption. Include steps for: 1. Removing the server from the load balancer rotation. 2. Verifying traffic is no longer being sent to it. 3. Backing up critical data and configurations. 4. Shutting down the server. 5. Removing it from monitoring and inventory systems. 6. Terminating the cloud instance or physical machine.
Add Escalation Contacts
Generate a standard 'Escalation Contacts' section for a runbook.
Create a markdown-formatted 'Escalation Contacts' section for a runbook about the '[Service Name]' service. Include placeholders for the Primary On-Call, Secondary On-Call, Team Lead/Manager, and any relevant external dependency teams (e.g., '[Database Team]'). Use a table format for clarity.
Cloud Resource Cleanup Procedure
Generate a runbook for identifying and decommissioning unused or underutilized cloud resources to optimize costs.
Outline a runbook for identifying and cleaning up unused or underutilized cloud resources in '[Cloud Provider]' for cost optimization. Include steps for: 1. Running cost analysis reports in '[Cloud Billing Tool]'. 2. Identifying orphaned resources like unattached disks, old snapshots, or idle databases. 3. Getting approval for deletion. 4. Automated or manual deletion procedures. 5. Verification of cost savings after cleanup.
Turn these prompts into a reusable workspace
Save your favourite prompts once, reuse them with Alt+P, keep a live Table of Contents of long chats, and export conversations when you're done.
Add ChatBoost to Chrome — It's free