Dependencies or Parent/Child Relationships

5 minutes ago, Stuart Weenig said:

As far as i'm aware, you can't manually edit ERIs. However, you can easily write a static PropertySource that statically tags those devices. You'd then also need to write the companion TopoSource to tie them together, unless you were planning on manually adding ERIs that are already referenced by an existing TopoSource, which isn't likely. They pretty much have to work in conjunction with each other.

That said, after you get the topology awareness into LM, you still need to specify your entry point, which orients the dependency tree from root to tip. Let's keep this conversation going because I think we can do what you're looking to do.

You think we can do it!

What would it take to have a call with you to discuss further? We are an MSP and need this capability ...."yesterday :)" to decrease the number of tickets created by dependent devices.

Just for reference:

I am familiar with the TopologySources/Mapping/Root Cause Analysis....pretty slick.

I even circled back and retested...again...using these two datasets. Neat concept but not a solution for our requirements.