Should not be set on hosts, better on services, especially end user ones
(like business rules ones). The key is to not tag important IT services,
only end users one, so when there is a problem, Shinken will automatically
compute the root problem business impact.

But for low level one like this one, can help to separate low impact from
others in the WebUI.


Jean

On Fri, Mar 15, 2013 at 2:09 PM, DessaiImrane <notifications@github.com>wrote:

> In etc/packs/virtualization/vmware/vm/services/tools.cfg:
>
> > @@ -0,0 +1,7 @@
> > +define service{
> > +   service_description           VM Tools
> > +   use            generic-service
> > +   register       0
> > +   host_name	  vmware-vm
> > +   check_command  check_esx_vm_tools
> > +}
>
> Ok ! I usualy forget to use business_impact as I use them on hosts only
> (and subsequent services get the same BI)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/naparuba/shinken/pull/780/files#r3390717>
> .
>