--- title: "Configuring system event notifications using the CLI" slug: "configuring-system-event-notifications-using-the-cli-5" tags: ["Product Usage", "CMS 11.x", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "IVX 11.x", "Customer", "Network Security"] updated: 2026-09-09T11:11:22Z published: 2026-09-09T11:11:22Z canonical: "docs.trellix.com/configuring-system-event-notifications-using-the-cli-5" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring system event notifications using the CLI Use the commands in this topic to customize system event notifications for each user and to configure which events trigger notifications. > [!WARNING] > Important > > You cannot view most Central Management System high availability (HA) events as described in this topic, and cannot configure which of those events trigger notifications. For a list of the HA events and their severity, see the *Central Management System* *High Availability Guide*. ### Viewing system events You can view all system events, or the system events that are currently enabled to trigger notifications, ordered by their severity. **To view all system events:** 1. Go to CLI configuration mode: ```plaintext hostname > enable hostname # configure terminal ``` 2. View the events: ```plaintext hostname (config) # email notify event ? ``` **To view enabled system events and their severity:** - View the events by severity: ```plaintext hostname > show email events ``` ### Enabling email notification **To enable receiving of email notifications:** ```plaintext hostname > enable email ``` ### Configuring system event notifications for each user **To configure system event notifications for each user:** 1. Go to CLI configuration mode: ```plaintext hostname > enable hostname # configure terminal ``` 2. View the current configuration: ```plaintext hostname (config) # show email ``` 3. Specify the severity of events for which each user should receive notifications. - To receive "info" events: ```plaintext hostname (config) # email notify recipient class info ``` - To stop receiving "info" events: ```plaintext hostname (config) # no email notify recipient class info ``` - To receive "failure" events: ```plaintext hostname (config) # email notify recipient class failure ``` - To stop receiving "failure" events: ```plaintext hostname (config) # no email notify recipient class failure ``` 4. Specify the notification format: - To receive detailed notifications: ```plaintext hostname (config) # email notify recipient detail ``` - To receive summarized notifications: ```plaintext hostname (config) # no email notify recipient detail ``` 5. Specify the scan event (*aborted, started, stopped, error (example: when continuous scan fails for any reason), paused or unmounted*): ```plaintext hostname (config) # email notify recipient scan-details ``` ### Configuring which events trigger notifications **To configure which events trigger notifications:** 1. Go to CLI configuration mode: ```plaintext hostname > enable hostname # configure terminal ``` 2. View the current configuration as described in [Viewing system events](/network-and-platform/docs/configuring-system-event-notifications-using-the-cli-5#viewing-system-events) . 3. To enable an event: ```plaintext hostname (config) # email notify event ``` 4. To disable an event: ```plaintext hostname (config) # no email notify event ``` 5. Verify your changes: ```plaintext hostname (config) # show email events ``` 6. Save your changes: ```plaintext hostname (config) # write memory ``` ### Examples This example stops admin@acme.com from receiving "info" notifications and changes the message format to a summary. ```plaintext hostname (config) # show email ... Email notification recipients:  admin@acme.com (all events, in detail)  operator@acme.com (failure events only, in detail)  user3@acme.com (all events, in detail) ... hostname (config) # no email notify recipient admin@acme.com info hostname (config) # no email notify recipient admin@acme.com detail hostname (config) # show email ... Email notification recipients:  admin@acme.com (failure events only, summarized)  operator@acme.com (failure events only, in detail)      user3@acme.com (all events, in detail) ``` This example disables log file rotations from triggering event notifications: ```plaintext hostname (config) # no email notify event syslog-rotation ``` This example disables DOP (depth of processing) overloads from triggering event notifications: ```plaintext hostname (config) # no email notify event avc-overload ``` The `avc-overload` event is an "info" level event that is generated for DOP overloads. DOP overloads occur when there is CPU contention for an MVX engine. If an overload occurs often, it can affect email and file analysis and potentially result in false negatives. If an appliance consistently has less than 30% DOP, it is overloaded. This may not be an issue if an overload happens for only a few minutes a week, but if there are overloads for several hours of every work day, the MVX engine should be allotted more CPU time.