server-management

Guide production server management with process control, monitoring, and scaling strategies.

Updated Aug 23, 2026

Search Tags:#monitoring #logging #scaling #process-management #server-management #health-checks

Ready to run

npx skills add https://github.com/thimmarques/gestao-inteligente --skill server-management-thimmarques

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: server-management
Source: https://github.com/thimmarques/gestao-inteligente/tree/main/.agent/skills/server-management
Command: npx skills add https://github.com/thimmarques/gestao-inteligente --skill server-management-thimmarques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams design and operate reliable server infrastructure by applying principled process management, monitoring, and scaling decisions, reducing downtime and firefighting.

Core Features & Use Cases

Process Management: guidance on choosing and using PM2, systemd, and container orchestration to maximize uptime.
Monitoring & Health: strategies for metrics, health checks, alerting, and log management to detect and respond to issues early.
Scaling & Resilience: frameworks for horizontal/vertical scaling, auto-scaling considerations, and disaster recovery planning.
Use Case: a production service that needs zero-downtime reloads and predictable performance under load.

Quick Start

Configure a standard production-ready server management plan for your current stack.

Frequently Asked Questions about server-management

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

FAQPage Schema

What is the best way to configure process management for zero-downtime Node.js reloads?▼

Zero-downtime Node.js reloads require principled process management using PM2 or systemd to orchestrate restarts. This approach applies guardrails to prevent downtime, ensuring predictable performance under varying load by controlling application lifecycles directly.

How do I set up server monitoring and health checks for containerized services?▼

Server monitoring for containerized services involves configuring metrics collection, health checks, and alerting strategies to detect issues early. This approach establishes structured log management to respond to production anomalies and maintain system reliability.

When do I need horizontal or vertical scaling for my production server infrastructure?▼

Horizontal and vertical scaling are needed when production services face varying load demands. This approach provides frameworks for auto-scaling considerations and disaster recovery planning, guiding decisions to maximize uptime and prevent resource exhaustion.

Can I use this server management approach with distributed systems and container orchestration?▼

Yes, this server management approach applies to distributed systems and containerized services. It guides scaling strategies and process control decisions across complex architectures, requiring knowledge of process managers and disaster-recovery planning to prevent downtime.

Why does my production service experience downtime during deployments under heavy load?▼

Production downtime during deployments under heavy load occurs without principled process control and zero-downtime reload strategies. Applying structured monitoring, auto-scaling considerations, and guardrails prevents firefighting and ensures reliable service restarts.

Do I need prior knowledge of PM2 and systemd to apply these server reliability strategies?▼

Yes, applying these server reliability strategies requires existing knowledge of process managers like PM2 and systemd. The approach builds on this foundation to guide monitoring, logging, and scaling decisions for production infrastructure.