Why does runZero show a different number of assets to our other systems?

Asset counts in runZero may differ from what you see in other systems. In most cases, runZero will show lower counts, and there are several reasons for this.

1. Different counting methods: Some systems count IP addresses rather than actual devices. Since a single asset in runZero can have multiple IPs, runZero will show a lower total in this case.

2. Active vs. all devices: runZero typically counts only live or recently seen assets. Other systems might count all devices, even ones that are no longer active on the network.

3. Different expiration settings: Each system may have different rules for how long it keeps asset data. For example, runZero might be configured to remove stale assets after 30 days, while the other system might keep records for 90 days.

4. Filtering outdated data: Some connectors in runZero ensure that only recent data is imported to avoid cluttering your inventory with old info. Other systems may include much older records in their totals.

5. Differences due to deduplication: When importing data, runZero will try to deduplicate entries. If two records appear to refer to the same machine, runZero may keep only the newer one. Another system might count both.

6. Multiple records on one asset: Sometimes several sets of attributes from a foreign source will be different enough that they can’t be deduplicated, but will match the same asset. In that situation several sets of attributes from the same source can end up on one asset. This can make the total count appear lower.

In summary, comparing asset counts between runZero and other systems isn’t always simple. To make a fair comparison, you need to understand how each system calculates its totals and make sure you’re comparing the same set of assets.