Can confirm on 23.4 P2 using RHEL 9.4 PSQL. Will check on newer release

Same in following version

NNMi 24.2 P1  RHEL9.4  PSQL. I wonder if its the twice use of wild card and positioning

In short, this attribute is not intended to be used in filters, and will probably excluded from the dropdown in the future:

R&D had an internal discussion on this:

1)
"neighborHostedOn" is not meant to be used as "ADDITIONAL FILTERS" either for Node Groups or Interface Groups.

2)
"neighborHostedOn" was developed to create a custom correlation between the neighboring nodes.


For Ex:
Let's consider a scenario,
Node-A is connected to Node-B (assume Node-B is a leaf node or connected ONLY through Node-A).
Node-A goes down, then "Node Down" incident is generated for Node-A.
Node-B - BGP Peer is down, then "BGP Peer Down" incident is generated for Node-B.
Now, the requirement is, when we already know, Node-A is down, and also, Node-B is connected ONLY through Node-A, then instead of a separate incident for "BGP Peer Down", "neighborHostedOn" was developed to create a "Correlation Rule", so that, "Node Down" becomes a parent and "BGP Peer Down" becomes its child incident.

3)
In conclusion, "neighborHostedOn" should not be used as "ADDITIONAL FILTERS" either for Node Groups or Interface Groups.

4)
The attribute 'neighborHostedOn' should ideally be excluded from the drop-down list of Attributes. However, this change cannot be implemented immediately due to its complex logic and interdependencies with other components. A careful assessment and gradual approach will be necessary to ensure this modification doesn't disrupt existing functionalities. I will also notify the development team about this issue so that it can be addressed in future releases.