Alarm/en: Difference between revisions
Jump to navigation
Jump to search
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 7: | Line 7: | ||
Some alarms don't require setup. E.g. if you break the applied license, by exceeding the allowed number of registered [[{{Link}}Object|objects]] or the end date of the license, it will be shown as an alarm. | Some alarms don't require setup. E.g. if you break the applied license, by exceeding the allowed number of registered [[{{Link}}Object|objects]] or the end date of the license, it will be shown as an alarm. | ||
If you need to get noticed about something that is not included in the standard alarms, it's possible to create alarms specific for your installation. If you are interested in more information about these possibilities, contact [mailto: | If you need to get noticed about something that is not included in the standard alarms, it's possible to create alarms specific for your installation. If you are interested in more information about these possibilities, contact [mailto:em@enghouse.com Servicedesk]. | ||
[[Category:Term{{Langcat|Alarm}}]] | [[Category:Term{{Langcat|Alarm}}]] | ||
Latest revision as of 12:57, 22 June 2023
Alarm
Alarms in Pro 9 are warnings to help you monitor that the system is working properly.
Alarms related to integrations (e.g. logging of calls or an AD/HR integration) require setup in the Log surveillance view and in the Node settings view.
Some alarms don't require setup. E.g. if you break the applied license, by exceeding the allowed number of registered objects or the end date of the license, it will be shown as an alarm.
If you need to get noticed about something that is not included in the standard alarms, it's possible to create alarms specific for your installation. If you are interested in more information about these possibilities, contact Servicedesk.