Entity duplication

When you monitor multiple items for an entity in SolarWinds Observability SaaS, you may see multiple entities monitoring the same thing.

Duplicate entities might be caused by adding a single entity multiple times to monitor different aspects for the entity or by using multiple agents to monitor the same thing.

Duplicate hosts

If you monitor a server added by the Network Collector and at the same time, you monitor it using an SolarWinds Observability Agent with the host monitoring plugin, you might encounter duplicate entities in SolarWinds Observability SaaS.

This table lists the options you might have used to deploy the Network Collector and Agent respectively.

SolarWinds Observability Agent with network-collector plugin	SolarWinds Observability Agent with host-monitoring plugin
Network Collector uses the Agent with network-collector (SiteConnected) plugin Add a network device SolarWinds Observability Self-Hosted uses the Agent with network-collector (CloudConnected) plugin Connect SolarWinds Observability Self-Hosted to SolarWinds Observability SaaS with Platform Connect	SolarWinds Observability Agent with the host monitoring plugin: Add a self-managed host Add an AWS cloud account Add an Azure cloud account Run the SolarWinds Observability Agent as a Docker image or Kubernetes deployment and Enable host monitoring plugin

Duplication in Azure resources

Entities are created for each Azure resource, and the display name of these entities are the Azure storage account names. However, Azure storage accounts can contain multiple resources. As a result, the Entity Explorer contains two entities with identical names for the Azure Blob Storage and Azure Files entity types.

Database/host duplication

In the following case, you can manually relate the entities to resolve the duplication.

• Manually link a database entity to a host