I believe you need to create an Extended Object that does this:
And then use your Discovery Job conditions to say
Extended Object where Value1 as String does not contain ""
Yes, we are using this method today, but a Discovery Job using an Extend Object it's very running very long time that a Discovery Job without Extend Object. I'm trying to do this without Extend Object, during the training on 7 version I have see this new feature but I'm not remember how.
Thanks for your proposition.
I'm not sure if you'd want to try doing this, but you could create a NSH script job that does the same thing. You could have the script job output a file, and then have your discovery job look for that file. Just an idea...
How about adding the "/usr/products/signatures" as a part to the component template, and then choose add an include for "SC-pla*".
I think that the Include/Exclude configuration lists does not allow to filter during the component discovery. This list is only used during an audit. Isn't it ?
Ah, I guess I misunderstood your question.
For now, wildcards (*, ?) for parts don't seem to be supported. I'm not sure what exactly you want to accomplish, but if you're looking for all those files, perhaps you can still use a component with an include and snapshot. That snapshot should show just those files.
How can I use a snapshot in a Discovery Job ?
What I mean is add the "/usr/products/signatures" as a part to the component template, and then choose add an include for "SC-pla". Run a discovery job with maybe just the condition that OS=Linux or something like that. Then snapshot the components. The snapshot should only contain the SC-pla files.
If this is not sufficient for your purposes and really only want the discover job to discover components on servers that have an SC-pla* file, then Greg's method above is probably best until we can wildcard parts.