Note: Information here is based on the following app version: 1.0.0.
To install the Alerting app:
- Create a chart config file, such as
app.yamlwith content similar to the following:
externalHostname: www.obcerv.local ingress: annotations: kubernetes.io/ingress.class: "nginx" nginx.org/mergeable-ingress-type: "minion"
externalHostnameparameter must match the DNS name configured for the Web Console.
- Your ingress controller may require custom annotations on the ingress (this example is for ingress-nginx).
- Install the chart:
helm install -f app.yaml obcerv-app-alerting itrs/obcerv-app-alerting \ --version 1.0.0.XX --devel -n itrs --wait
The Alerting page in the Web Console is divided into three sections:
- Options header — allows you to define groups and filters to organise monitored entities.
- Alerts section — shows the most recent alerts sorted by groups.
- Details section — shows the signal information associated with the selected alert.
The options header allows you to Filter or Group results on the page in order to focus on only the relevant information.
You can Group by one or more attributes or dimensions. You will see a prompt to start the expression when typing in the field.
The Alerts section will change to a folder based list when grouping is enabled.
You can Filter by one or more attributes or dimensions. You will see a prompt to start the expression when typing in the field.
When data is grouped, filters operate at the group level so that a group is included in the displayed results if any of its children are included in the filter. Children that do not match the filter are also displayed as part of the group.
The Alerts section shows a list of all alerts received in the selected time interval in chronological order.
|Dimension||Shows the entity that triggered the alert by listing its dimensions in hierarchical order.|
|Severity||Severity level of the alert. Colour coded to match the highest severity.|
|Age||Time since the alert was triggered.|
This section shows all signals contributing to an alert. Alerts are organised hierarchically so that the signals section of a selected entity shows the severity of its children as signals.
A parent entity inherits the maximum severity of its children. However, if an entity is snoozed then its severity is not taken into account when determining the severity of the parent entity.
You can expand a specific signal to see the changes in that metric over time. An expanded signal shows the changes to severity status on the left-hand side and the changes to the value of the metric on the right-hand side.
An entity is snoozed if it has the
snoozed attribute. Currently, Snooze messages are only sent by Geneos based on user-actions in Active Console.
snoozed attribute can have one of the following string values:
none: No triggered snooze events on the entity itself, its logs, or metrics.
partial: At least one triggered snooze event on an entity metric or log and none on the entity itself.
full: At least one triggered snooze event on the entity itself.