To stop monitoring an entity, ensure that data about the entity is no longer sent to SolarWinds Observability, and then remove the entity.
If you only delete the entity in SolarWinds Observability, the data will continue flowing to SolarWinds Observability, and the entity will be recreated.
Task 1: Ensure data is no longer sent to SolarWinds Observability
If data about the entity is ingested using an agent or library, such as SolarWinds Observability Agent or Network Collector, ensure the data is no longer sent. The procedure depends on the entity type.
Database instances and hosts
Delete the SolarWinds Observability Agent that provides data about the database instance or host. See Uninstall the Agent.
Delete the network device from the Network Collector:
Log in to the Network Collector Web Console. See Log in to the SolarWinds Platform Web Console.
Click Settings > Manage Nodes.
Select the node and click Delete.
The device is deleted in the Network Collector. No data is sent from the device to SolarWinds Observability.
Remove the associated APM library:
- Disable and uninstall the .NET Library on Windows, Linux, Azure App Service, or NuGet package.
- Uninstall the Java Library.
- Remove the Node.js Library.
- Uninstall the PHP Library.
- Uninstall the Python Library.
- Remove the Ruby Library.
If RUM was configured for a website, SolarWinds recommends removing the script that you added to the website.
Task 2: Remove the entity from SolarWinds Observability
Hover over the table row, and click the vertical ellipsis () in the far-right column. (If necessary, use the horizontal scroll bar to access the column.)
- Click Remove, and then click Remove again in the confirmation dialog.
The entity is removed from SolarWinds Observability, but the historical data is retained. Calculations using this data are not affected.
If the entity re-appears in the Entity Explorer, delete it again. This can be caused by latency, long message queues, or other connection issues.