Notifications and Operational Events

Faddom generates Notifications and Operational Events for application map-related changes as well as administrative activities. These can be viewed by clicking the bell icon in the top right of the Faddom interface.

Operational Events are issues that may impact the stability of your environment or break functionality. These require attention and action.

Notifications are informational updates about changes in your environment, providing a chronological feed of activity.

The bell icon screen displays both categories with clear visual distinction, with Operational Events prioritized by default.

The Notifications screen is a log showing all historic notifications. You can access this by clicking the bell icon in the top right. If there are new items, a number badge will indicate the count.

Operational Events advise you of changes or issues that have happened recently and require your attention. Events are displayed in a table showing severity, date created, affected asset, and event type.

You can filter events by clicking the filter icon, which allows you to refine by date range, severity level, event type, status, affected asset, or application map. To resolve an event, select it using the checkbox and choose the appropriate action. Once you have attended to an event, it will disappear from the Operational Events view and move to the Notifications screen.

You can filter events by clicking the filter icon, which allows you to refine by date range, severity level, event type, status, affected asset, or application map. To resolve an event, select it using the checkbox and choose the appropriate action. Once you have attended to an event, it will disappear from the Operational Events view and move to the Notifications screen.

You can select all Operational Events and clear them all at once if desired. When an event is closed (either individually or in bulk), Faddom records the username of the user who closed it.

To configure notifications for Operational Events, you must first define notification channels to specify the targets, then create notification subscriptions.

Operational Events can also be viewed directly from Application Maps, allowing you to see which events are affecting specific applications.

When viewing an application map, Faddom uses a red dot icon in the map list to alert you to any Operational Events that may affect the functionality of the servers within that map.

To view all events associated with a map:

This provides context-aware visibility, helping you understand how operational issues impact your business applications.

For information on how external monitoring systems can push events into Faddom, see External Events Integration

Notification channels define how Faddom sends alerts about Operational Events.

Available channel types:

Channel details include:

You can send email notifications in two ways:

Local (Default): Uses Faddom as the mail server (Postfix). Simply enter recipient emails and a sender address. To use your domain (e.g., faddom@yourcompany.com), ensure DMARC permissions are configured.

Azure Note: For Azure Marketplace deployments, port 25 is blocked by default (used by Faddom Postfix). Refer to Microsoft's Troubleshoot outbound SMTP connectivity problems in Azure documentation.

Remote: To use your own SMTP server, select the Remote option and enter the required credentials.

You can push Faddom events to any service or system that supports webhooks with a custom message. See our guide How to Push Notifications via Webhooks.

Choose the SNMP server and port you are using.

You can push Faddom alerts to your ServiceNow instance. This will create an incident in ServiceNow with full details of the alert. See ServiceNow Integration for CMDB and Incident Creation.

You can push Faddom alerts directly to your Syslog server. Select the Syslog type and enter the required details

If you need to disable the built-in SMTP server for security reasons, use the following commands: