Forum Discussion
Like i mentioned before, yes, i believe there is a way. However, I don't know the exact code, someone from LM would need to provide that (they should).
That said, i've built hundreds of datasources and it's never really been an issue to just use the same code that produces the instance list in the first place right in the collection script. In many cases, the same call that grabs the list of instances from the target can include the metrics as well so you're still only doing one call.
So if your query calls the database to grab the list of instances during discovery, do the same thing during collection, but expand your query to include the metrics. Then loop through the rows of that query outputting the wildvalue along with the metrics.
I pinged the ME's channel and linked to this thread. If there is some way of enumerating wildaliases from within an AD batchscript, it's not something I'm aware of. There could be some new way I'm not aware of.
I wrote countless official LM modules that did the same thing with respect to running the same code in AD and collection, to get the instances.
*About 2 seconds after posting this I received this from the MEs:
datasourceinstanceProps.each{ instance, instanceProperties ->
instanceProperties.each{
it ->
println it.wildValue
}
}
def listOfWildValues = datasourceinstanceProps.values().collect { it.wildvalue }
Related Content
- 11 months ago
- 11 months ago
- 3 months ago
- 8 months ago