Groups created from Inventory are static snapshots; dynamic grouping by service membership not supported

Products

• DX Operational Observability
• DX Operational Intelligence
• DX OI SaaS

Issue/Introduction

When creating a Group from the Inventory view with a filter applied (for example Service does not contain .*), the group does not behave dynamically. The applied filter is not retained as the group definition, and the group's membership does not update automatically as entities are discovered or as they are later mapped to services.

Two symptoms are observed:

• Group membership is limited to the entities currently loaded/selected in the Inventory grid rather than the full filter result set (e.g., a filter matching 1548 entities produces a group of only 100, or 346 after expanding the list).
• The original filter criteria cannot be viewed or edited after the group is created.

The goal of the use case is to automatically assign all newly discovered entities to a "Default Entities" catch-all group and automatically remove them once they are mapped to a service, in order to reduce the number of entities listed as "Devices Not in Services," while keeping the group usable for CPA configuration and Universe inclusion and keeping the group name out of the services_impacted alarm attribute.

Environment

DX Operational Observability On-Premise, Release 26.

Cause

By design, creating a Group from the Inventory view stores a static snapshot of the entities currently loaded/selected in the grid. The filter is converted into a fixed name IN (...) criteria list at creation time rather than being persisted as a live query. Because membership is a fixed list, the group does not auto-include newly discovered entities and does not auto-remove entities once they are assigned to a service. The Group criteria builder ("Base Attribute for Definition") does not currently offer a service-membership attribute, so dynamic grouping based on whether an entity belongs to a service is not possible.

Resolution

Dynamic, service-membership–based grouping is not available in DX O2 26.1. This has been raised as an enhancement request for a future release. The enhancement requests that the product:

1. Expand the list of attributes available in the Create/Edit Group criteria builder to include service-membership attributes (e.g., serviceNames) with operators such as "is empty" / "does not exist" / "does not contain."
2. Persist these as live, re-evaluated criteria (dynamic group membership) rather than converting them into a static entity list at creation time.
3. Keep the group criteria viewable and editable after the group is created.

Interim options:

• Group membership can be kept current outside the UI by using the DX O2 REST APIs, a scheduled job that queries the Inventory API for entities not in any service and synchronizes the group membership via the Group Management API.
• Note that the Service Insights "Devices Not in Services" count is driven by service membership, not group membership; placing entities in a group (even a dynamic one) does not by itself reduce that count. A plain group correctly stays out of the services_impacted alarm attribute and remains usable for CPA and Universe scoping.