Deleting Servers and Devices

When you need to remove servers or devices from your Server Scout monitoring setup, it's important to follow the proper process to avoid issues and ensure a clean removal. This guide covers everything you need to know about deleting monitored resources.

Before You Delete: Understanding the Impact

Deletion in Server Scout is permanent and cannot be undone. When you delete a server or device, you'll lose all associated data, including:

  • The complete server record
  • All stored metrics history
  • All mount point data
  • All plugin data and custom configurations
  • All alert conditions specific to that server
  • All notification history related to that server

For network devices, the device configuration is completely removed from the poller, stopping all monitoring activities.

Recommended Removal Process

To avoid authentication errors and ensure a clean removal, follow this three-step process:

1. Uninstall the Agent from the Server

First, remove the Server Scout agent from the server itself. SSH into your server and run:

sudo serverscout --uninstall

This command will:

  • Stop the Server Scout service
  • Remove the agent files
  • Clean up configuration files
  • Remove any scheduled tasks or cron jobs

2. Wait for the Server to Show as Offline

After uninstalling the agent, wait a few minutes for the server to appear as "Offline" in your Server Scout dashboard. This confirms that the agent has stopped sending data and won't attempt further connections.

3. Delete from the Dashboard

Once the server shows as offline, you can safely remove it from your dashboard:

  1. Navigate to your Server Scout dashboard
  2. Locate the server you want to delete
  3. Click the three-dot menu (⋯) on the server card
  4. Select "Delete" from the dropdown menu
  5. Confirm your decision in the confirmation dialogue that appears

The server will be immediately removed from your dashboard along with all associated data.

Deleting Network Devices

For network devices (routers, switches, etc.), the process is simpler since there's no agent to uninstall:

  1. Click the three-dot menu on the device card
  2. Select "Delete"
  3. Confirm in the dialogue box

The device configuration will be removed from the SNMP poller, and all monitoring will cease immediately.

What Happens if You Skip Agent Uninstallation?

If you delete a server from the dashboard without first uninstalling the agent, the agent will continue attempting to send monitoring data to Server Scout. These requests will be rejected with 401 authentication errors because the server no longer exists in the system.

While these errors won't harm your infrastructure, they will:

  • Generate unnecessary log entries on the server
  • Consume small amounts of network bandwidth
  • Create confusion during troubleshooting

The agent will eventually stop after several failed attempts, but it's much cleaner to uninstall it properly.

Bulk Deletion Considerations

If you're removing multiple servers, consider staggering the process rather than deleting everything simultaneously. This approach helps you:

  • Monitor for any unexpected issues
  • Ensure each uninstallation completes successfully
  • Maintain better oversight of your infrastructure changes

Recovery Options

Remember, once deleted, there's no way to recover the historical data or configurations. If you might need the server again in the future, consider whether temporary disabling might be more appropriate than permanent deletion.

For servers you're rebuilding or temporarily taking offline, you might prefer to leave them in the dashboard and simply reinstall the agent when ready, preserving your historical metrics and alert configurations.

By following this systematic approach, you'll ensure clean removals without leftover processes or authentication errors cluttering your logs.

Frequently Asked Questions

How do I properly delete a server from ServerScout monitoring?

Follow a 3-step process: First, SSH into your server and run 'sudo serverscout --uninstall' to remove the agent. Wait for the server to show as offline in your dashboard. Finally, click the three-dot menu on the server card and select Delete to remove it from the dashboard.

What happens if I delete a server without uninstalling the agent first?

The agent will continue attempting to send monitoring data to ServerScout, which will be rejected with 401 authentication errors. While this won't harm your infrastructure, it generates unnecessary log entries, consumes bandwidth, and creates confusion during troubleshooting until the agent eventually stops.

Can I recover a deleted server and its data in ServerScout?

No, deletion in ServerScout is permanent and cannot be undone. When you delete a server, you lose all associated data including the complete server record, metrics history, mount point data, plugin configurations, alert conditions, and notification history. Consider temporary disabling instead if you might need the server again.

What data gets deleted when I remove a server from ServerScout?

All data associated with the server is permanently removed, including the complete server record, all stored metrics history, mount point data, plugin data and custom configurations, alert conditions specific to that server, and all notification history related to that server.

How do I delete network devices from ServerScout?

Deleting network devices is simpler since there's no agent to uninstall. Click the three-dot menu on the device card, select Delete, and confirm in the dialogue box. The device configuration will be removed from the SNMP poller and all monitoring will cease immediately.

What does the serverscout uninstall command do?

The 'sudo serverscout --uninstall' command stops the ServerScout service, removes all agent files, cleans up configuration files, and removes any scheduled tasks or cron jobs. This ensures a complete cleanup of the monitoring agent from your server.

Should I delete multiple servers at once from ServerScout?

It's better to stagger the deletion process rather than removing multiple servers simultaneously. This approach helps you monitor for unexpected issues, ensures each uninstallation completes successfully, and maintains better oversight of your infrastructure changes.

Was this article helpful?