Notification
A notification is a signal sent by a monitoring tool when the performance of the IT infrastructure component it tracks, crosses a certain threshold. It could be a status update, warning, announcement of a crisis, or its resolution. For example, “Server A disk space is at 80%”, or “Beta application server is at 65%”.
Alert logs
The list of notifications from the same resource with the same metric that have been grouped together to reduce noise.
Note: You can customise the Alert logs columns, and save the columns related to that particular source or for all sources.
Alert
In Freshservice, an alert is an indicator of an issue. It is built by grouping similar notifications, for example, those for a common resource with a common metric. An alert conveys the message, severity, and last updated details on the Alerts List page. All alerts in Freshservice are subjected to Alert Rules wherein they must meet certain conditions to be converted into incidents.
Basic grouping
The process of bundling similar notifications from a common resource with a common metric to avoid duplicity and repetition.
Automated grouping
The process of using Freddy machine learning algorithm to attach incoming alerts to open incidents. This reduces noise at the incident level and leads to the creation of contextually rich and current incidents.
Alert ID
A unique alphanumeric code used to identify a specific alert.
Notification fields
Specific components of the payload shared by a monitoring tool, for example, the information contained in a notification. These could include names of resource, metric, metric value, description, severity, and so on.
Resource
A resource is an IT infrastructure component being monitored. It could be a service, an application, a node, or the host name.
Metric name
A specific performance related aspect of the resource being monitored. Examples include CPU utilization, Throughput, and so on.
Metric value
Value of the monitored metric. For example, 50% of the CPU utilised.
Node
Denotes the Mac address or the IP address of the resource.
Message
A message in context of an alert describes the associated issue.
Severity
Severity describes the potential impact of an alert and the urgency with which it must be addressed. In Freshservice, we map the severity values used by monitoring tools to the ones used within Freshservice, so that all notifications can be interpreted using a common standard.
Description
A description of the issue for which a notification is sent.
Tags
Tags help users classify alerts using keywords. This helps team members to quickly understand an issue and act upon it.
Occurrence time
Refers to the time of creation of an alert. This can be viewed on the Alert Detail page.
Associations
Denotes the incidents that are related to a specific alert. This can be found in the Alert Detail page.
Notes
Refers to notes shared by teams regarding specific alerts.
Activities
Over its lifecycle, an Alert Group undergoes multiple status changes as registered in the Alert List. Check the Activities tab to understand what exactly caused the change in status of an Alert Group and at what time.
