Why does the Entity Viewer state tree show only some of the dataviews that Active Console shows?

The Active Console displays every dataview on a sampler, while the Entity Viewer state tree may omit some dataviews when the active context matches more than 10,000 entities. There is no indication in the Entity Viewer that some dataviews have been left out.

What limits which dataviews the state tree shows? Copied

Before building the folders, the Entity Viewer state tree runs a query that keeps at most 10,000 entities. Entities with a warning and critical severity, as well as those that are snoozed, are kept first, then the remaining places are then filled in display-name order. A dataview that does not get a place is omitted from every folder. The number on the folder indicates the entities that were kept, and the folder does not show that more dataviews exist.

That 10,000 limit decides which entities are available to the state tree. Additionally, the state tree also limits how many of those entities it draws on screen:

• The tree draws at most 50 folders.
• Each folder draws at most 25 entities, or 1,000 after you click the count on the folder. Full state tree is shown while that drill-in is active.

When either of those is reached, the tree shows ...another N entities or More items available. Click to view more.

How can I resolve this? Copied

The 10,000 limit is not configurable; however, two other views can read the stored entities directly:

• Search tree — searches the stored entities by name first, then applies the 10,000 limit only to the matches. A dataview hidden in the normal tree can appear here if its name matches.
• Search all entities — is not affected by the 10,000 limit. It returns up to 20 stored matches.

To locate the missing dataview, start by checking whether it exists in ITRS Analytics.

1. Search for the dataview name (not the sampler name) in either place:

   • Search all entities — clear any selected context, and under Status include Inactive.
   • Search tree in the state tree — use the same dataview name.
   Expand table

   Result	Meaning	Next step
   No matches	The dataview is not in the index, so the state tree cannot show it.	Stop here and investigate ingestion or publishing instead.
   A match is returned	The dataview is stored. The state tree left it out because of the 10,000 limit.	Continue to the next step.

2. Narrow the context so fewer than 10,000 entities match. Create or edit a context with a filter that covers only the relevant area, for example, one managed entity, or one managed entity and one sampler. Then:

   a. Clear any text in Search tree.

   b. If the tree shows Full state tree, click it to leave that drill-in before you compare folders.

   c. Open the sampler folder again and look for the dataview.

3. Read the number on the folder to see whether the limit still applies.

   • Below 10,000 — this context is under the cap. If the dataview is still missing from the first 25 names, click the folder count and scroll. The count only includes entities that match the context, the current drill-in, and the activity window.
   • Exactly 10,000 — the context is still too wide. Narrow the filter further and repeat this step.

Note

Entities that do not have the state tree group-by keys are listed under Excluded Entities rather than in the folders. The Query Service disk size, signal history, and CPU settings do not change which names the state tree keeps.