Forum Discussion

JosiahBenoit's avatar
JosiahBenoit
Icon for Neophyte rankNeophyte
5 months ago

Resource Explorer

Hi, When utilizing the newly released "Resource Explorer" I am attempting to Group by: "Resource Type" these grouping has a lot of "No Resource Type" and "Unknown" resources being grouped together, ...
  • JosiahBenoit's avatar
    JosiahBenoit
    5 months ago

    Alright, I think I have this figured out to make the Resource Explorer mostly usable.  My org did not really apply property sources or the ones they did apply were not updated. From what I can tell in my sandbox once the property sources are updated and applied to the resources, that seems to allow for logical groups inside of resource explorer.  

Shack's avatar
Shack
Icon for Advisor rankAdvisor
5 months ago

We use a property source to tag device types based on its static group.  ERI's were not consistent or would misclassify device types so now we just rely on the static group and tag them that way.  All of our customers have the same nested folder architecture so this is what works for us.  

Example below showing just the beginning of the if statement

import com.santaba.agent.groovyapi.expect.Expect;
import com.santaba.agent.groovyapi.snmp.Snmp;
import com.santaba.agent.groovyapi.http.*;
import com.santaba.agent.groovyapi.jmx.*;
import org.xbill.DNS.*;
 
def staticgroup = hostProps.get("system.staticgroups")
 
if(staticgroup =~ "Switch"){
println "auto.cmdb.devicetype=Switch"
}else if(staticgroup =~ "Firewall"){
println "auto.cmdb.devicetype=Firewall"
}else if(staticgroup =~ "Router"){
    println "auto.cmdb.devicetype=Router"
 
I just checked in resource explorer and was able to group devices by the println name. 
  • Anonymous's avatar
    Anonymous
    5 months ago

    That's exactly what we do. But we're still trying to find a use case that lasts more than 3 minutes of ooohs and aaahs.