Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


The main role of this feature is to allow users to have in one "indicator" the aggregation of other states. This indicator can provide a unique view for users focused on playing different roles.

Typical roles:

...

Let's take a simple example of a service delivery role for an ERP application. It mainly consists of in the following IT components:

  • 2 databases, in high availability, so with one database active, the service is considered to be up
  • 2 web servers, in load sharing, so with one web server active, the service is considered to be up
  • 2 load balancers, again in high availability

...

With business rules, you can have an "indicator" representing the "aggregated service" state for the ERP service! Shinken Enterprise already checks all of the IT components one by one including processing for root cause analysis from a host and service perspective.

...

The X of: expression may be configured with different values depending on the needs. The supported expressions are described below:

...


Sometimes, you do not want to specify explicitly the hosts/services contained in a business rule, but prefer use using a grouping expression such as *hosts from the hostgroup xxx*, *services holding lablel yyyor *hosts which name matches regex zzz*.

To do so, it is possible to use a *grouping expressionwhich expression which is expanded into hosts or services. The supported expressions use the following syntax:

...

.. note:: A business rule expression always has to be made of by a host expression (selector if you prefer)
AND a service expression (still selector) separated by a coma when looking at service status.
If not so, there is no mean to distinguish a host status from a service status in the expression.
In servicegroup flag case, as you do not want to apply any filter on the host (you want ALL services which are member of the XXX service group, whichever host they are bound to),
you may use the host selector expression. The correct expression syntax should be:
``bp_rule!*,g:my-servicegroup``
The same rule applies to other service selectors (l, r, t, and so on).

...