Configuring Notification Settings

Use Notifications to have Axonius send a notification email to configured email addresses according to these settings.

To configure Notification Settings:

1. From the top right corner of any page, click . The System Settings page opens.
2. In the Categories/Subcategories pane of the System Settings page, expand System, and select Notifications.

• Notifications email address - Configure a comma-separated list of email addresses to receive an email:
  • When there is a connection issue with any of the adapter connections, the email contains a table of affected adapters with relevant details. Connection failure emails can also go to more addresses for each adapter. See Also notify on connection failure.
  • When a node has not communicated for over three hours.
  • When the available free disk space is below the limit defined (if configured).
• Notifications webhook address - Configure the webhook URL to receive a message. The message sent is the same as the message included in the email.
  • When there is a connection issue with any of the adapter connections.
  • When the available free disk space is below the limit defined (if configured).
• Notify when a discovery cycle runs longer than X hours (default: off) - Enable this option to get a notification when a discovery cycle runs longer than the number of hours you set. Axonius checks every 10 minutes, so the notification can arrive up to 10 minutes late. Axonius sends one notification for each cycle, counted from the start of the cycle, for both scheduled and manual cycles.
  • Number of hours (required, default: 12) - Set the number of hours after which a running discovery cycle triggers a notification. You can enter a decimal value, for example 1.5. Enter 0 to send no notification.
  • The notification appears on the Monitoring page and is sent by email to the Notifications email address. It states how long the cycle has been running and the current phase of the cycle.
• Enable notifications for low disk space (percentage %)
  • Visible for customer-hosted (on-premises / private cloud) deployments only.
  • When toggled on, the system monitors the available free disk space percentage for all nodes and creates critical or warning notifications based on the following settings:
    • Critical notifications: notify when free disk space is below (percentage %) (optional, default: 5) - Set the percentage of free disk space, below which the system creates a critical notification.
    • Warning notifications: notify when free disk space is below (percentage %) (optional, default: 10) - Set the percentage of free disk space, below which the system creates a warning notification.
    • Minimum days between critical notifications (required, default: 1) - Set the minimum number of days that need to pass since the last time a critical disk space notification based on percentage was created per node.
    • Minimum days between warning notifications (required, default: 7) - Set the minimum number of days that need to pass since the last time a warning disk space notification based on percentage was created per node.
• Enable notifications for low disk space (GB)
  • Visible for customer-hosted (on-premises / private cloud) deployments only.
  • When toggled on, the system monitors the available free disk space in GB for all nodes and creates critical or warning notifications based on the following settings:.
    • Critical notifications: notify when free disk space is below (GB) (optional, default: 10) - Set the amount of free disk space (GB), below which the system creates a critical notification.
    • Warning notifications: notify when free disk space is below (GB) (optional, default: 15) - Set the amount of free disk space (GB), below which the system creates a critical notification.
    • Minimum days between critical notifications (required, default: 1) - Set the minimum number of days that need to pass since the last time a critical disk space notification based on available space in GB was created per node.
    • Minimum days between warning notifications (required, default: 7) - Set the minimum number of days that need to pass since the last time a warning disk space notification based on available space in GB was created per node.
• Send notification when a scheduled fetch failed to trigger - Enable this option to activate adapter fetch notifications. The emails of these notifications list each affected adapter connection in a separate row. A table has up to 100 rows, and a line below it shows how many more connections are not listed. When enabled, you can configure the following sub-options:
  • Notify if an adapter did not complete a fetch in the last X days - When toggled on, sends an email notification if an adapter has not triggered any fetch within the specified number of days.
    • Number of days (default: 7) - Set the number of days after which an adapter with no fetch is flagged.
  • Notify if an adapter did not complete a successful fetch in the last X days - When toggled on, sends an email notification if an adapter has not completed a successful fetch within the specified number of days.
    • Number of days (default: 7) - Set the number of days after which an adapter with no successful fetch is flagged.
  • Notify when a successful fetch returns 0 assets (default: off) - When toggled on, sends one daily email notification that lists each adapter connection whose most recent successful fetches all returned 0 assets. This option works only when Send notification when a scheduled fetch failed to trigger is enabled and a Notifications email address is set.
    • Number of consecutive successful fetches with 0 assets (default: 1, minimum: 1) - Set the number of consecutive fetches that return 0 assets before Axonius lists the connection. Failed fetches don't count and don't reset the count. Fetches that ran before the upgrade don't count.

• Notify when at least one gateway is running an outdated agent version - When selected, weekly notifications are sent when at least one gateway is running a version lower than the Axonius instance and can be upgraded. Additionally, a banner is displayed in both the Gateways page and in the details drawer of the outdated gateway. See Upgrading a Gateway.

  In order to send notifications via email, the email settings in External Integrations must be configured. See Configuring Email Settings.