Should an Application Service go "red" if network equipment goes "red"?

[Johannes]

We use Tag-based Application Services only.

This works fine for automatically adding the infrastructure CIs belonging to the application, but other common CIs are naturally not added, i.e. nobody is aware if e.g. some network component fails. 

I can solve this by grouping the relevant network CIs with a Dynamic CI Group, add the necessary key_values, and recalculate the AS. This way the AS goes red if something in the DCIG goes red.

But, the application might be running just fine on its servers. It might be the users that can not access the application, so maybe I should rather create the relationship from the application's Offering(s) to the DCIG's Offering(s). I believe the latter is more common to model manually (the tag-way is a bit of a "hackaround", but quite easy to do).
However, if we did top-down discovery, network components would be added to the map, and would thus make the AS go red, so I believe it makes sense to do an AS depends on DCIG. 

Any opinions on this?

[Mark Manders]

It doesn't matter to an end user creating a case if the application is down or just a network component preventing them to log in. It also doesn't matter to your Servicedesk, since the incidents are all reporting an issue with the application. So making the application red is a great indicator that something is going on that (could or) is impacting the application service. The fact that there may be workarounds in place to limit the impact, does nothing with the effect of the network components having (possible) impact on the AS.

[Johannes]

Hi @Mark Manders 
Thanks for you answer.
As you say, it does not matter to the end user what component is causing the downtime.
If we go for the more common approach, i.e. DCIG -> SO -> SO, I believe we need to script some to make it show on impacted services on e.g. the incident form, but that is ok for us to do.
With DCIG -> AS -> SO, impacted services will work OOTB.

But what I am looking for is how people use the Application Services e.g. in Service Operator Workspace -> Service Dashboard; will people monitoring the AS here feel that the propagation from the DCIGs would be mainly noise, as their own application runs fine? I would think so if the DCIG is to "broad".

And how about the usage of e.g. Enterprise Architecture Workspace and Digital Portfolio Workspace, will these show to much irrelevant information if we to either?