Notifications
- Last Updated: April 5, 2026
- 4 minute read
- Flowmon Products
- Flowmon Application Performance Monitoring
- Documentation
The configuration of notifications contains two parts:
-
Action profiles – configuration of actions that can be assigned to notifications.
-
Notifications – configuration of notification conditions.
Notifications
A new notification can be added using the New notification button. In the notification table next to each notification, there is an Edit link to edit the notification and a Remove link to remove it. The first column of the table titled Active also contains toggles to activate/deactivate the respective notifications.
Description of notification editing:
-
Name – the name of the notification.
-
Metric – the monitored metric.
-
Min. transaction count – the minimum number of all transactions that must take place in the defined time frame for the notification to be activated.
Threshold – the threshold value for the set metric
| Metric | Unit |
|---|---|
| APM index | real number ( 0.0 – 100.0 ) |
| Application response time 95% | milliseconds |
| Application response time 99% | milliseconds |
| Avg. app. response time | milliseconds |
| Median of app. response time | milliseconds |
| Error count | count |
| Parallel users count | count |
| Total amount of data | bytes |
| Total transaction count | count |
| Avg. network transport time | milliseconds |
| Max. network transport time | milliseconds |
-
Time frame – the period for which the selected metric is evaluated.
-
Repeat – the setting of notification repetition.
-
Every event – every time the threshold of the set metric is exceeded, an event is triggered.
-
After clearing – a new event occurs only if the previous event instance was marked as “cleared”. See Chapter Alerts.
-
After X hours – repetition of an event after a specified number of hours after the previous event occurrence.
-
-
Suppress from/to – suppress notification for a certain time interval
-
Actions profile - setting of notification actions; see heading Actions.
-
New profile – creating of a new action profile.
-
Update profile – editing of the selected action profile.
-
Store – setting whether to save events in Alerts; see Chapter Alerts.
-
Valid for – selection of applications or groups for which the notification will be evaluated.
-
Save – saving changes to the form.
An example of notification configuration if there is a drop in a 5-minute APM index under the value of 95.
| Parameter | Value |
|---|---|
| Name | APM under 95 |
| Metric | APM index |
| Min. transaction count | 10 (Notification will only be active if there were at least 10 transactions over the last 5 minutes.) |
| Threshold | 95 |
| Time frame | 5 minutes |
| Repeat | after 1 hour (notifications will be sent max. once an hour) |
| Save | YES (notifications will be recorded in Alerts) |
| Valid for | all applications |
Action profiles
Actions, that will occur when notification conditions are met can be configured here. A new action profile can be added using the New profile button. In the action profiles table next to each profile, there is an Edit link to edit the profile and a Remove link to remove it.
After clicking New profile, fill in the profile name and then use the New action button for adding new actions.
Supported actions are:
-
Email
-
System log
-
Script
-
SNMP
-
HTTP request
-
Recipients – a list of recipients’ email addresses separated by commas.
-
Text – text of the notification. If the use default box is selected, you do not need to enter any text and the predefined notification text is used.
-
Subject – the subject of the notification email. If the use default box is selected, you do not need to enter any text and the predefined text is used.
In the notification text, you can use macros that are replaced by a specific value if an event occurs.
List of macros:
| Macro | Will be replaced by |
|---|---|
| $NAME | Notification name |
| $PERIOD | Beginning of the period for which the threshold has been exceeded |
| $TIME | Time the event occurred |
| $VALUE | The current value of the monitored metrics |
| $APP | Name of the application |
| $GROUP | Name of the group of transactions |
| $COND | Condition (metric + threshold) |
| $TFRAME | Time frame set in the notification |
| $ID | Event ID |
System log
Recording of the event in the Syslog local log.
-
Facility – syslog facility.
-
Priority – syslog priority - event priority.
-
Text – event text. Macros referred to in the previous heading Email can be used in the text.
Script
A system script is called at an event occurrence.
-
Full path – path to the script on the APM server.
-
Parameters – parameters of script call. The macros described above (under the Email heading) can be used here.
A script must be recorded on Flowmon, for example, using SCP (SSH). The recommended location for the script is the home directory of the flowmon user (/home/flowmon). The script must have (chmod +x script) for the flowmon user.
SNMP
An SNMP trap is invoked at an event occurrence.
-
SNMP version – version selection: v2c or v3
-
SNMP parameters – parameters of the SNMP trap command. For example:
-c public 200.200.200.200 '' -
SNMP OIDs For example:
\$PERIOD \$TFRAME \$VALUE \$COND \$TIME \$GROUP \$APP \$ID \$NAME
The MIB file can be downloaded by clicking on this icon: 
HTTP request
An HTTP request is called at an event occurrence.
-
URL – URL or IP address of an HTTP request
-
Method – HTTP method (GET or POST)
-
URL parameters – parameters of the URL formatted as name1=value1&name2=value2 . The macros described above (under the Email heading) can be used here. Example:
name=\$NAME&app=\$APP&value=\$VALUE