There has been a lot of discussion around dependencies. But I have not seen anything about including Application Monitors in Dependencies. I had set up some Dependencies for Application Monitors, they did not work and upon further reading I found that the state that controls Dependencies is "Down". Since Application Monitors don't use the Down state, you cannot control reporting of Application Monitor events using Dependencies. Even further investigation with SW Support confirmed my findings.
Let me lay out a scenario as an example... You have an application that is running on a database engine and both the database engine and application have login ports for use or management of the environment. I want to have the ability to suppress (make Unreachable) the port events for the application if the application is down. As well I want to suppress the application, application port and database engine port events if the database engine is down.
The cure for this would be for SW to make available an option to choose the state of the Parent that would trigger the Dependency reaction. In this case, if the application or database engine reached a "Critical" state, the appropriate children would become Unreachable.