Forum Discussion

SteveBamford's avatar
SteveBamford
Icon for Neophyte rankNeophyte
3 years ago
Solved

Stopping properties from Cascading down to lower levels.

So I have been working on integrating data from our CMDB into LogicMonitor for use with alerting and observability and integration, all is going well, and I do have a work around for this, my quest...
  • Anonymous's avatar
    Anonymous
    3 years ago

    As far as I know, there's no way to stop this behavior. It's one of the key pieces of functionality that is the "Logic" in "LogicMonitor". 

SteveBamford's avatar
SteveBamford
Icon for Neophyte rankNeophyte
3 years ago
42 minutes ago, Stuart Weenig said:

As far as I know, there's no way to stop this behavior. It's one of the key pieces of functionality that is the "Logic" in "LogicMonitor". 

Thanks Stewart, I have just amended my script to set the sharedservice.dependancy field to None on the Hypervisor Instance and VM instance if applicable, which works just as well for me and will still show the cluster (Device) data if you expand the field anyway, so I think I can live with that, and in all honesty I think having at least a link to the cluster as the CMDB DeviceId field will at least give anyone the top level data in the CMDB.