Resource Explorer

Question

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, when I drill into them I clearly know what type of resources what they are, some switches, routers, net storage and other such things.&nbsp; Does anyone know a way to "Tag" the resources in the "Resource Explorer" to clean this up? If, you have a better training then something provided on LM Academy or you can find via of a Google search that would be much appreciated.&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;

josiahbenoit · Accepted Answer

Alright, I think I have this figured out to make the Resource Explorer mostly usable.&nbsp; 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.&nbsp;&nbsp;

mike_moniz · Answer

Resource Explorer works based on properties on devices, so changes would need to be done there rather than in the explorer itself (afaik). Hovering over Resource Type shows that it's using the "predef.externalResourceType" property. I believe this is coming from the Topology/ERI system that finds relationships/connections between devices but I'm not sure. I don't know too much about this system or exactly how this property is set. I would suggest checking that you have added/updated all the addERI_* PropertySources as I believe these are what sets them (but I might be wrong).
&nbsp;

stuart_weenig · Answer

That's right Mike_Moniz . For us, it makes all the default grouping unusable since the coverage is so poor. It would be nice if we could specify which property to use for the "device type" built in grouping field.
We've been struggling to find a use case for this besides, "oh look, this is a colorful view". However, if you ever find yourself looking for a reason to use a feature in a product, that's a clear indicator that they built the feature without actual users in mind.

shack · Answer

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.

stuart_weenig · Answer

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.

mike_moniz · Answer

Well you can use any property you want for groups by typing them in instead of one of the aliases. I did see that https://www.logicmonitor.com/blog/hybrid-observability-made-easy-introducing-logicmonitors-new-ui mentions a possible future "alias manager" that perhaps would let you modify them? Assuming it's talking about the same aliases.

Forum Discussion

Resource Explorer

10 Replies

Related Content

New UI Impact Series - Resource Explorer

Resource Tree is BACK!

LogSource Resource Mapping Confusion

Resource Property Filters on the New UI Preview

glob expression excluding resources not working

Recent Discussions

LogicMonitor Integration with ServiceDesk Plus

Testing LogicModules without updating?

User defined "host dead" status

Certs

Resource Dead parameter