Managing alerts & notifications

the factry portal provides automatic alerting to monitor the health, performance, and licensing status of your historian installations and collectors alerts help detect connectivity issues, system overload, storage problems, and license risks before they cause downtime managing alerts alerts are managed per installation via https //portal factry cloud/installations viewing alerts go to factry portal navigate to installations click the eye icon next to your historian server open alert configurations you can filter alerts by installation, severity, or status creating custom alerts installations → eye icon → alert configurations → + add alert complete the following fields name – clear and descriptive name activation delay – duration the condition must remain active before triggering template – select a message template frequency – interval for repeated notifications if still active escalate to factry after – duration after which factry is notified if the alert remains high custom alerts can be edited, disabled, deleted, or silenced editing alerts for each alert in the configuration list, you can edit the alert configure notification channels (e g email, webhook) enable or disable the alert delete the alert silence the alert acknowledging alerts when an alert fires use the ack button to mute notifications until the issue is resolved alerts that are not acknowledged will trigger reminder notifications based on the configured frequency acknowledging suppresses notifications but does not resolve the underlying issue silences (planned maintenance) silences temporarily suppress notifications (maximum 7 days) silence all alerts for an installation installations → eye icon → alert configurations → +add silence rule silence a single alert installations → eye icon → alert configurations → silence alert ( ) silencing does not disable the alert, it only suppresses notifications during the selected period auto created alerts the factry portal automatically creates alerts for all new instances they are created when a historian first connects to the portal a new collector is onboarded auto created alerts cannot be modified cannot be deleted can be linked to notification channels auto created alerts for historians no monitoring data received for > 5 minutes issue writing data to the time series database cpu or memory usage > 80% disk usage > 85% free disk space < 5000 mb license expiry in less than 30 days auto created alerts for collectors no heartbeat for > 5 minutes bad health no data collection (while health = collecting) more points with bad quality than with good quality cpu or memory usage > 80% disk usage > 85% free disk space < 5000 mb managing notification channels to add or modify notification channels, go to settings → notification channels or visit https //portal factry cloud/notification channels for full details on configuring and linking notification channels, see the docid\ gnrkmaecwhmpv7vqg5jat page best practice link alerts to at least one notification channel use silences during planned maintenance review auto created alerts when onboarding new instances