Delete entities
To stop monitoring an entity, ensure that data about the entity is no longer sent to SolarWinds Observability SaaS, and then remove the entity.
Task 1: Ensure data is no longer sent to SolarWinds Observability SaaS
This task is only relevant for the following entities:
If data about the entity is ingested using an agent or library, such as SolarWinds Observability Agent, ensure the data is no longer sent. The procedure depends on the entity type.
If you only delete the entity in SolarWinds Observability SaaS, the data will continue flowing to SolarWinds Observability SaaS, and the entity will be recreated.
Database instances and hosts
Delete the SolarWinds Observability Agent that provides data about the database instance or host. See Uninstall the Agent.
Services entities
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.
Websites
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 SaaS
-
In the Entity Explorer, display the entities in List View, and then select the entity you want to delete. Management buttons for the selected entities will be displayed above the table.
You can also select the entity in the area overview, such as Network area overview, or open the entity details view.
- Click Remove, and then click Remove again in the confirmation dialog.
As an alternative, you can hover over the table row, click the vertical ellipses () in the far-right column, and select the option in the menu. On device details view, find the vertical ellipsis in the top-right corner of the view.
The entity is removed from SolarWinds Observability SaaS, 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.