Bug 534750 (RHQ-1516)

see: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208307#4208307

all monitoring sofware can uninventory components. In jon can't taken this. Don't should be there?

That's why this issue exists :) Need to implement. There is a "secret" way to do this now IIRC - in the URL, you put "?debug=true" and the uninventory button is enabled.  However, its not available normally because under normal conditions (i.e. if the service really does still exist on the agent side) then the agent will rediscover the service and commit it back into inventory automatically, undoing the uninventory that was just performed.

This issue is to document the need to be able to tell the agent, "ignore this resource, even if you discover it again". Right now, only servers can be igonred, not child services.

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1516
This bug is duplicated by RHQ-2173

mass add of key word FutureFeature to help track

Another instructive discussion on the issue
http://community.jboss.org/message/534970

*** Bug 568917 has been marked as a duplicate of this bug. ***

in the new GWT interface, you can uninventory resources.

However, the still-outstanding issue is how to IGNORE services.

Because I may want to uninventory, say, my CPU services because I don't want to monitor them. However, the next time we run a service scan, they will be re-discovered and automatically re-inventoried.

We need a way to "ignore" service resources (just like we can for servers) so they are not re-imported into inventory, even if they exist.

Just my two cents... I would suggest that we leverage a consistent way to import, remove, discovery, and ignore all resources whether platform, server, or service.

For example, the Auto-Discovery Queue would be a nice way to "ignore" any resource that you do not want in inventory and still give the user a way of un-ignoring it later. I would also suggest that we expand the auto-discovery queue to support discovery invocations and auto-import functions. For example:

Filter by COMMITTED resources:
   Select one or more COMMITTED resource and "Perform Child Resource Discovery"

Filter by COMMITTED resources:
   Select one or more COMMITTED resource and enable/disable "Auto Import Child Resources"

Filter by NEW resources:
   Select one or more NEW resources and enable/disable "Ignore This Resource"

Also, with such functionality, it may be useful to add resource types of Platform, Server, and Service to the filter capabilities.

And while we're at it, maybe get rid of the Auto-Discovery Queue and move this to the actual resource pages with an added filter for the resource's inventory state (COMMITED, NEW, etc).

(In reply to comment #12)
> in the new GWT interface, you can uninventory resources.
> 
> However, the still-outstanding issue is how to IGNORE services.
> 
> Because I may want to uninventory, say, my CPU services because I don't want
> to monitor them. However, the next time we run a service scan, they will be
> re-discovered and automatically re-inventoried.
> 
> We need a way to "ignore" service resources (just like we can for servers)
> so they are not re-imported into inventory, even if they exist.

we can now ignore services, too. this has recently been added as a feature. I think we can close this BZ.