skills.rest
virahitvin8
virahitvin8COMMUNITY
Explore all skills by this author →
GitHub

server-management

Guides server process management, monitoring, logging, and scaling decisions for production operations.

2|Updated May 30, 2026
Search Tags:#devops#monitoring#process management#health checks#server management#scaling#pm2
One-click install
npx skills add https://github.com/virahitvin8/crafty-gis --skill server-management-virahitvin8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: server-management
Source: https://github.com/virahitvin8/crafty-gis/tree/main/GIT_STAR/.agent/skills/server-management
Command: npx skills add https://github.com/virahitvin8/crafty-gis --skill server-management-virahitvin8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running production servers involves many decisions—choosing process managers, setting up monitoring, planning scaling, and handling incidents—and this Skill provides structured decision frameworks instead of memorized commands. ## Core Features & Use Cases - Process Management Guidance: Decision tables for choosing between PM2, systemd, Docker, and Kubernetes based on your application type. - Monitoring & Alerting Strategy: Frameworks for what to monitor (availability, performance, errors, resources) and how to set alert severity levels. - Scaling & Troubleshooting Playbooks: Symptom-to-solution mappings for scaling decisions and a prioritized 5-step troubleshooting sequence. - Use Case: Your Node.js API is experiencing high CPU usage in production. Use this Skill to decide between vertical and horizontal scaling, configure PM2 clustering, and set up health checks and log rotation. ## Quick Start Ask the AI to help you design a monitoring and process management strategy for your Node.js production server using PM2.

Frequently Asked Questions about server-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between PM2 and systemd for process management?▼

Use PM2 for Node.js applications when you need clustering and zero-downtime reloads. Use systemd for any application on Linux when you want native OS integration and automatic startup on boot.

What should I monitor on a production server?▼

Monitor four categories: availability (uptime, health checks), performance (response time, throughput), errors (rate and types), and resources (CPU, memory, disk). Set alert severity levels so critical issues trigger immediate action.

When should I scale vertically vs horizontally?▼

Scale vertically (more RAM/CPU) as a quick fix for single instances. Scale horizontally (more instances) for sustainable, distributed growth. Use auto-scaling when traffic is variable or spiky.

How do I troubleshoot a server that is not responding?▼

Follow a priority order: check if the process is running, review logs for errors, check resources (disk, memory, CPU), verify network (ports, DNS), then check dependencies like databases and external APIs.

What are common server management anti-patterns to avoid?▼

Avoid running as root, ignoring log rotation, skipping monitoring, relying on manual restarts, and having no backup schedule. Instead use non-root users, structured logging, auto-restart configuration, and regular backups.

Related Skills

Explore More Software Engineering Skills→
michsindlingermichsindlinger
1

Infrastructure Provisioning Skill

Automate cloud infrastructure provisioning with Terraform across DigitalOcean, AWS, and GCP.

Community
Advanced
allthingslinuxallthingslinux
1

alert-management

Route alerts and coordinate incidents across PagerDuty, Alertmanager, and Slack.

Official
Advanced
terna-ccterna-cc

sentry-setup

Configure Sentry SDK and integrate Pino for automated log forwarding.

Official
Basic
Zehong-WangZehong-Wang

modal

Run Python functions serverlessly in the cloud with GPU support.

Community
Advanced