hiteshpatel601
| Server | OS | Provider |
| 1 | Windows | Hetzner |
| 2 | Linux - Ubuntu | Hetzner |
| 3 | Linux - Ubuntu | Digital Ocean |
| 4 | Linux - Ubuntu | IONOS |
| 5 | Linux - Ubuntu | IONOS |
| 6 | Windows | |
| 7 | Windows | Clouldy |
| 8 | Linux - Ubuntu | IONOS |
Prerequisites to Begin
1. Server Access
- ✅ SSH access to Linux/Ubuntu servers
- ✅ RDP or admin access to Windows servers
2. Network & Firewall Rules (optional if no internet restrictions)
- ✅ Allow outbound traffic to New Relic endpoints (TCP 443)
- ✅ If needed, whitelist these New Relic domains/IP ranges:
New Relic Network Requirements
3. Server Info to Share
- Operating System and version for each server (already Shared)
- Hostname and internal IP
- Role (web, DB, app server, etc.)
- Business priority (helps tailor alert thresholds)
4. Admin Account
- Create a New Relic account or invite us to yours
- Provide admin-level access for setup
🛠️ Setup Plan
Step 1: Install New Relic Infrastructure Agents
- Linux/Ubuntu: install via shell script or package manager
- Windows: install via MSI or PowerShell
Step 2: Enable Server-Level Alerts
- Alerts for:
- Server down
- High CPU/RAM usage
- Low disk space
- Network issues
- Application crash (if applicable)
- Synthetic Monitoring
Step 3: Dashboard Creation
- Custom dashboard showing server health, online status, CPU, RAM, disk, and real-time analytics
Step 4: Notification Channels
- Set up alerts via:
Step 5: Optional Add-ons
- Synthetic monitors for uptime checks