About guardrails

Edit online

Use guardrails partition event groups based on your operations team requirements.

For the purposes of this documentation, we will take the example of a scope-based group that has grouped together events that have occurred in multiple locations:
  • Brighton, UK
  • London, UK
In this example, there are two separate operations teams, one team resolving incidents associated with the Brighton location, and another separate team resolving incidents associated with the London location.
By setting guardrails, you can partition the scope-based group so that Brighton events are grouped into one group, and London events into a separate group. This is what those two event groups look like after partitioning has been performed.
Figure 1.
alert viewer
The following screen shot highlights the two groups.
Figure 2.
alert viwere with two groups highlighted
You can see that the scope of the Brighton group has been defined by prefixing the Brighton location value to the previous value of the ScopeId field.
Figure 3.
You can see that the scope of the London group has been defined by prefixing the London location value to the previous value of the ScopeId field.
Figure 4.

For example, based on defined conditions, you can partition the events in a scope-based, temporal, or topological group into separate event groups based on factors such as technology or group or user ownership. The supergroups that are created from these partitioned groups allow you to do things such as generating distinct tickets for different technologies, or to assign to different user groups.