Notifications

StorONE watches its own health continuously — hardware, replication, capacity, security, and more — and raises notifications when something changes state or needs attention. A notification target tells StorONE where to send those notifications: an email inbox, an SNMP trap receiver, a Syslog server, a Seq log server, or a Slack channel. You can configure as many targets as you like, and each target has its own filter for which notifications it should receive.

Configuring more than one target is common and useful — for example, a Slack target for the whole team to see day-to-day Warning-level events at a glance, alongside an email target scoped to Error and Fatal events for whoever's on call. Since each target has an independent severity and category filter, you can fan the same stream of events out to different audiences without changing anything about how StorONE generates them.

This chapter covers configuring notification targets. To search or browse notifications StorONE has already generated, see Browsing Notification History.

Severities and categories

Every notification StorONE generates has two properties that targets filter on:

• Severity (event level) — how serious the notification is, from least to most severe: Verbose, Debug, Information, Warning, Error, Fatal. When you set a target's minimum level, it receives that level and everything more severe. If you don't set one, it defaults to Information — which excludes only the low-level Verbose/Debug diagnostic noise.
• Category (module) — which part of the system the notification came from. The categories are: Notifications, Platform, Resources, Snapshots, ThinProvisioning, HighAvailability, Replication, AutoTiering, Networking, Licensing, Encryption, FileSystem, Protocols, Audit, Reports, and MultiSystemManager. A target can listen to all of them or to a specific subset — for example, a target dedicated to your networking team might only need the Networking and HighAvailability categories.

If you create a target without specifying categories at all (neither --all nor --modules), it listens to every category — this is equivalent to passing --all explicitly, not to listening to nothing.

Email

Email is usually the first target people configure, since it doesn't require any external infrastructure beyond an SMTP server. Because multiple email targets share the same outgoing mail server, that server only needs to be configured once, system-wide — individual email targets then just say who receives what.

Configuring the mail server

Using the web interface

1. Open Administration > Notifications, select the Email tab, and open the mail server settings.
2. Enter the Mail Server Address, Mail Server Port, and (if your server requires authentication) Mail Server Username and Mail Server Password.
3. Optionally set Send From Address if notifications should appear to come from a different address than the username.
4. Choose the encryption method your mail server expects, and whether StorONE should validate the server's certificate.
5. Confirm to save.

Using the CLI

notifications settings email edit [--mailServerAddress=<text>] [--mailServerPort=<numbers>]
    [--mailServerUsername=<text> --mailServerPassword=<password>] [--sendFromAddress=<text>]
    [--secureSocketOption=<name>] [--enableCertificateValidation | --disableCertificateValidation]

Option	Description
--mailServerAddress=<text>	Mail server address.
--mailServerPort=<numbers>	Mail server port.
--mailServerUsername=<text>	Mail server username.
--mailServerPassword=<password>	Mail server password.
--sendFromAddress=<text>	The address notifications are sent from, if different from the username (or if no username is set).
--secureSocketOption=<name>	Encryption to use when connecting to the mail server: None (no encryption), Auto (let the implementation choose — the default), SslOnConnect, StartTls, or StartTlsWhenAvailable.
--enableCertificateValidation	Validate the mail server's certificate (default).
--disableCertificateValidation	Skip certificate validation. Allows self-signed certificates, but is not secure — use only if the server is fully trusted.

You need to supply at least one field (or a certificate-validation flag) for this command to do anything.

Examples

Configure a mail server that requires authentication and STARTTLS:

notifications settings email edit --mailServerAddress smtp.example.com --mailServerPort 587 --mailServerUsername alerts@example.com --mailServerPassword "hunter2" --secureSocketOption StartTls

Change only the "from" address shown on outgoing notification emails:

notifications settings email edit --sendFromAddress noreply@example.com

You can check the current configuration with notifications settings email show, and reset it entirely with notifications settings email reset [--force] — useful if you're switching mail providers and want to start clean. Both take no other options besides reset's --force, which skips the confirmation prompt.

Adding an email target

An email target sends notifications to a single email address. If you need several people to receive the same alerts on different addresses, create one target per address.

Using the web interface

1. Open Administration > Notifications, select the Email tab, and click Add.
2. Under Name and Email, enter the Email address to notify, and optionally a Name for the target (if left blank, StorONE names the target after the email address).
3. Under Modules Selection, choose All to receive every category, or pick specific categories under Modules.
4. Set the minimum severity and batching options as needed, then confirm.

Using the CLI

notifications targets email add --email=<email> [--minLevel=<name>] [--all | --modules=<name...>]
    [--batchPostingLimit=<numbers>] [--batchPostingPeriodInSec=<numbers>] [--name=<name>]

Option	Description
--email=<email>	Email address to notify.
--minLevel=<name>	Minimum event level to notify about. Defaults to Information.
--all	Notify about all categories. This is also what happens if you omit both --all and --modules.
--modules=<name...>	Specific category names to notify about.
--batchPostingLimit=<numbers>	The maximum number of events to post in a single batch. Must be greater than zero. If omitted, StorONE batches up to 100 events at a time.
--batchPostingPeriodInSec=<numbers>	How often (in seconds) StorONE checks for events to send. Must be greater than zero. If omitted, StorONE checks roughly every 30 seconds.
--name=<name>	Name for the target in StorONE (must be unique across all targets). Defaults to the email address.

Examples

Add a simple email target that receives everything at the default severity:

notifications targets email add --email storage-alerts@example.com

Add a named target scoped to critical hardware and replication events only:

notifications targets email add --email oncall@example.com --name oncall-critical --minLevel Error --modules HighAvailability Replication

Add a target that batches events less aggressively (once a minute, up to 500 at a time) — useful for a noisy category you still want a record of, without flooding an inbox:

notifications targets email add --email audit-log@example.com --modules Audit --batchPostingLimit 500 --batchPostingPeriodInSec 60

Editing an email target

Using the web interface

1. Open Administration > Notifications, select the Email tab, select the target, and click Edit.
2. Update the fields you need under Name and Email and Modules Selection.
3. Confirm the change.

Using the CLI

notifications targets email edit <name> [--email=<email>] [--minLevel=<name>] [--all | --modules=<name...>]
    [--batchPostingLimit=<numbers>] [--batchPostingPeriodInSec=<numbers>] [--newname=<name>]
    [--disableTarget | --enableTarget]

Option	Description
<name>	Name of the target to edit.
--email=<email>	New email address.
--minLevel=<name>	Minimum event level to notify about.
--all	Notify about all categories.
--modules=<name...>	Specific category names to notify about.
--batchPostingLimit=<numbers>	The maximum number of events to post in a single batch. Must be greater than zero.
--batchPostingPeriodInSec=<numbers>	How often (in seconds) StorONE checks for events to send. Must be greater than zero.
--newname=<name>	New name for the target.
--disableTarget	Temporarily stop this target from receiving notifications, without deleting it.
--enableTarget	Re-enable a target that was previously disabled.

Examples

Point an existing target at a different address:

notifications targets email edit oncall-critical --email newoncall@example.com

Temporarily silence a target — for example, during planned maintenance — without losing its configuration:

notifications targets email edit oncall-critical --disableTarget

Re-enable it afterward, and widen it to include networking events:

notifications targets email edit oncall-critical --enableTarget --modules HighAvailability Replication Networking

Listing email targets

Using the web interface

Open Administration > Notifications and select the Email tab. All configured email targets are listed there.

Using the CLI

notifications targets email list [<name>] [--email=<email>]

Option	Description
<name>	Filter by target name.
--email=<email>	Filter by email address.

Example

notifications targets email list

Deleting an email target

Using the web interface

Open Administration > Notifications, select the Email tab, select the target, and click Delete.

Using the CLI

notifications targets email delete <name>

Option	Description
<name>	Name of the target to delete.

Example

notifications targets email delete oncall-critical

SNMP

An SNMP target sends notifications as SNMP traps to a network management station. This is a good fit if you already monitor your infrastructure through an SNMP-based tool and want StorONE events to show up alongside everything else.

Adding an SNMP target

Using the web interface

1. Open Administration > Notifications, select the SNMP tab, and click Add.
2. Under Name and IP, enter the Manager Address (the IP address of your SNMP trap receiver) and optionally a Name (defaults to the manager address if left blank).
3. Set the Manager Port (defaults to 162), Community String, and Trap Version as needed.
4. If using trap version v3, fill in the V3 Options — Context, Username, Auth Phrase, and Privacy Phrase.
5. Under Modules Selection, choose All or specific categories.
6. Confirm to create the target.

Using the CLI

notifications targets snmp add --managerAddress=<ip> [--name=<name>] [--managerPort=<numbers>]
    [--communityString=<text>] [--trapVersion=<trapVersion>]
    [(--v3Context=<text> --v3Username=<name> --v3AuthPhrase=<text> --v3PrivacyPhrase=<text>)]
    [--minLevel=<name>] [--all | --modules=<name...>]

Option	Description
--managerAddress=<ip>	IP address of the SNMP manager (trap receiver).
--name=<name>	Name for the target in StorONE (must be unique). Defaults to the manager IP address.
--managerPort=<numbers>	Manager port. Defaults to 162.
--communityString=<text>	The community string to use when sending a trap.
--trapVersion=<trapVersion>	SNMP trap version: V1, V2, or V3. Defaults to V2.
--v3Context=<text>	Context to use when sending a trap. Only meaningful with --trapVersion=V3.
--v3Username=<name>	Username for the auth security levels. Only meaningful with --trapVersion=V3.
--v3AuthPhrase=<text>	Pass phrase for the authNoPriv/authPriv security levels. Only meaningful with --trapVersion=V3.
--v3PrivacyPhrase=<text>	Pass phrase for the authPriv security level. Only meaningful with --trapVersion=V3.
--minLevel=<name>	Minimum event level to notify about. Defaults to Information.
--all	Notify about all categories. This is also what happens if you omit both --all and --modules.
--modules=<name...>	Specific category names to notify about.

Examples

Add a v2 trap target using the default community string field:

notifications targets snmp add --managerAddress 10.0.0.50 --communityString public

Add a named v3 trap target with authentication and privacy:

notifications targets snmp add --managerAddress 10.0.0.51 --name nms-secure --trapVersion V3 --v3Context storone --v3Username s1monitor --v3AuthPhrase "authPhrase123" --v3PrivacyPhrase "privPhrase123"

Add a target on a non-standard port that only reports HighAvailability issues at Warning or above:

notifications targets snmp add --managerAddress 10.0.0.52 --managerPort 1162 --minLevel Warning --modules HighAvailability

Editing an SNMP target

Using the web interface

1. Open Administration > Notifications, select the SNMP tab, select the target, and click Edit.
2. Update fields under Name and Manager Settings, V3 Options, and Modules Selection as needed.
3. Confirm the change.

Using the CLI

notifications targets snmp edit <name> [--managerAddress=<ip>] [--managerPort=<numbers>] [--minLevel=<name>]
    [--all | --modules=<name...>] [--communityString=<text>] [--trapVersion=<trapVersion>]
    ([--v3Context=<text>] [--v3Username=<name>] [--v3AuthPhrase=<text>] [--v3PrivacyPhrase=<text>])
    [--newname=<name>] [--disableTarget | --enableTarget]

Option	Description
<name>	Name of the target to edit.
--managerAddress=<ip>	New manager IP address.
--managerPort=<numbers>	Manager port.
--minLevel=<name>	Minimum event level to notify about.
--all	Notify about all categories.
--modules=<name...>	Specific category names to notify about.
--communityString=<text>	The community string to use when sending a trap.
--trapVersion=<trapVersion>	SNMP trap version: V1, V2, or V3.
--v3Context=<text>	Context to use when sending a trap.
--v3Username=<name>	Username for the auth security levels.
--v3AuthPhrase=<text>	Pass phrase for the authNoPriv/authPriv security levels.
--v3PrivacyPhrase=<text>	Pass phrase for the authPriv security level.
--newname=<name>	New name for the target.
--disableTarget	Temporarily stop this target from receiving notifications.
--enableTarget	Re-enable a previously disabled target.

Note: if the target didn't have v3 parameters set when it was created, you must supply all four (--v3Context, --v3Username, --v3AuthPhrase, --v3PrivacyPhrase) together the first time you set them — you can't add them one at a time.

Examples

Switch a target to a new manager address:

notifications targets snmp edit nms-secure --managerAddress 10.0.0.60

Upgrade a v2 target to v3, setting all the v3 parameters at once:

notifications targets snmp edit nms-secure --trapVersion V3 --v3Context storone --v3Username s1monitor --v3AuthPhrase "authPhrase123" --v3PrivacyPhrase "privPhrase123"

Listing SNMP targets

Using the web interface

Open Administration > Notifications and select the SNMP tab.

Using the CLI

notifications targets snmp list [<name>] [--ip=<text>]

Option	Description
<name>	Filter by target name.
--ip=<text>	Filter by manager IP address.

Example

notifications targets snmp list --ip 10.0.0.50

Deleting an SNMP target

Using the web interface

Open Administration > Notifications, select the SNMP tab, select the target, and click Delete.

Using the CLI

notifications targets snmp delete <name>

Option	Description
<name>	Name of the target to delete.

Example

notifications targets snmp delete nms-secure

Syslog

A Syslog target forwards notifications to a remote Syslog server over the network, using TCP or UDP.

Adding a Syslog target

Using the web interface

1. Open Administration > Notifications, select the Syslog tab, and click Add.
2. Optionally enter a Name (if left blank, StorONE names the target after the connection type and server address, e.g. TcpSyslog-10.0.0.5).
3. Under Syslog, choose the Connection Type (TCP or UDP), enter the Server Address, and optionally the Server Port and SSL Protocol.
4. Under Modules Selection, choose All or specific categories.
5. Confirm to create the target.

Using the CLI

notifications targets syslog add [--name=<name>] --connectionType=<name> --serverAddress=<text>
    [--serverPort=<outbound_port>] [--sslProtocol=<name>] [--minLevel=<name>] [--all | --modules=<name...>]
    [--batchPostingLimit=<numbers>] [--batchPostingPeriod=<numbers>]

Option	Description
--name=<name>	Name for the target in StorONE (must be unique). Defaults to the connection type (and server address, if provided).
--connectionType=<name>	The Syslog connection to use — TcpSyslog or UdpSyslog.
--serverAddress=<text>	Network address of the remote Syslog server.
--serverPort=<outbound_port>	Port on the remote Syslog server. Defaults to 1468 if not specified.
--sslProtocol=<name>	SSL/TLS protocol to use when connecting to the remote Syslog server. Defaults to no encryption.
--minLevel=<name>	Minimum event level to notify about. Defaults to Information.
--all	Notify about all categories. This is also what happens if you omit both --all and --modules.
--modules=<name...>	Specific category names to notify about.
--batchPostingLimit=<numbers>	The maximum number of events to post in a single batch. Must be greater than zero. If omitted, StorONE batches up to 1000 events at a time.
--batchPostingPeriod=<numbers>	How often (in seconds) StorONE checks for events to send. Must be greater than zero. If omitted, StorONE checks roughly every 2 seconds.

Examples

Add a basic TCP Syslog target on the server's default listening port:

notifications targets syslog add --connectionType TcpSyslog --serverAddress syslog.example.com

Add a named UDP target on a specific port, encryption-free (typical for UDP):

notifications targets syslog add --name legacy-syslog --connectionType UdpSyslog --serverAddress 10.0.0.70 --serverPort 514

Add a TCP target over TLS, scoped to Warning and above:

notifications targets syslog add --connectionType TcpSyslog --serverAddress syslog.example.com --serverPort 6514 --sslProtocol Tls12 --minLevel Warning

Editing a Syslog target

Using the web interface

1. Open Administration > Notifications, select the Syslog tab, select the target, and click Edit.
2. Update fields under Name and Syslog, and Modules Selection as needed.
3. Confirm the change.

Using the CLI

notifications targets syslog edit <name> [--connectionType=<name>] [--serverAddress=<text>]
    [--serverPort=<outbound_port>] [--sslProtocol=<name>] [--minLevel=<name>] [--all | --modules=<name...>]
    [--batchPostingLimit=<numbers>] [--batchPostingPeriodInSec=<numbers>] [--newname=<name>]
    [--disableTarget | --enableTarget]

Option	Description
<name>	Name of the target to edit.
--connectionType=<name>	The Syslog connection to use — TcpSyslog or UdpSyslog.
--serverAddress=<text>	Network address of the remote Syslog server.
--serverPort=<outbound_port>	Port on the remote Syslog server.
--sslProtocol=<name>	SSL/TLS protocol to use when connecting to the remote Syslog server.
--minLevel=<name>	Minimum event level to notify about.
--all	Notify about all categories.
--modules=<name...>	Specific category names to notify about.
--batchPostingLimit=<numbers>	The maximum number of events to post in a single batch. Must be greater than zero.
--batchPostingPeriodInSec=<numbers>	How often (in seconds) StorONE checks for events to send. Must be greater than zero.
--newname=<name>	New name for the target.
--disableTarget	Temporarily stop this target from receiving notifications.
--enableTarget	Re-enable a previously disabled target.

Examples

Move a target to a new server address:

notifications targets syslog edit legacy-syslog --serverAddress 10.0.0.80

Switch a target from UDP to TCP with TLS:

notifications targets syslog edit legacy-syslog --connectionType TcpSyslog --sslProtocol Tls12

Listing Syslog targets

Using the web interface

Open Administration > Notifications and select the Syslog tab.

Using the CLI

notifications targets syslog list [<name>] [--serverAddress=<text>]

Option	Description
<name>	Filter by target name.
--serverAddress=<text>	Filter by server address.

Example

notifications targets syslog list --serverAddress syslog.example.com

Deleting a Syslog target

Using the web interface

Open Administration > Notifications, select the Syslog tab, select the target, and click Delete.

Using the CLI

notifications targets syslog delete <name>

Option	Description
<name>	Name of the target to delete.

Example

notifications targets syslog delete legacy-syslog

Seq

A Seq target forwards notifications to a Seq structured-logging server, if your organization already uses one for centralized log search.

Adding a Seq target

Using the web interface

1. Open Administration > Notifications, select the Seq tab, and click Add.
2. Under Name and Server Url, enter the Server Url of your Seq server, and optionally a Name (defaults to Seq if left blank).
3. Under Modules Selection, choose All or specific categories.
4. Confirm to create the target.

Using the CLI

notifications targets seq add --serverUrl=<url> [--minLevel=<name>] [--all | --modules=<name...>]
    [--batchPostingLimit=<numbers>] [--batchPostingPeriodInSec=<numbers>] [--name=<name>]

Option	Description
--serverUrl=<url>	URL of the Seq server.
--minLevel=<name>	Minimum event level to notify about. Defaults to Information.
--all	Notify about all categories. This is also what happens if you omit both --all and --modules.
--modules=<name...>	Specific category names to notify about.
--batchPostingLimit=<numbers>	The maximum number of events to post in a single batch. Must be greater than zero. If omitted, StorONE batches up to 100 events at a time.
--batchPostingPeriodInSec=<numbers>	How often (in seconds) StorONE checks for events to send. Must be greater than zero.
--name=<name>	Name for the target in StorONE (must be unique). Defaults to Seq.

Examples

Add a Seq target that receives everything:

notifications targets seq add --serverUrl http://seq.example.com:5341

Add a named Seq target scoped to replication and auto-tiering activity:

notifications targets seq add --serverUrl http://seq.example.com:5341 --name seq-replication --modules Replication AutoTiering

Editing a Seq target

Using the web interface

1. Open Administration > Notifications, select the Seq tab, select the target, and click Edit.
2. Update the fields you need under Name and Server Url.
3. Confirm the change.

Using the CLI

notifications targets seq edit <name> [--serverUrl=<url>] [--minLevel=<name>] [--all | --modules=<name...>]
    [--batchPostingLimit=<numbers>] [--batchPostingPeriodInSec=<numbers>] [--newname=<name>]
    [--disableTarget | --enableTarget]

Option	Description
<name>	Name of the target to edit.
--serverUrl=<url>	New URL of the Seq server.
--minLevel=<name>	Minimum event level to notify about.
--all	Notify about all categories.
--modules=<name...>	Specific category names to notify about.
--batchPostingLimit=<numbers>	The maximum number of events to post in a single batch. Must be greater than zero.
--batchPostingPeriodInSec=<numbers>	How often (in seconds) StorONE checks for events to send. Must be greater than zero.
--newname=<name>	New name for the target.
--disableTarget	Temporarily stop this target from receiving notifications.
--enableTarget	Re-enable a previously disabled target.

Example

notifications targets seq edit seq-replication --serverUrl http://seq2.example.com:5341

Listing Seq targets

Using the web interface

Open Administration > Notifications and select the Seq tab.

Using the CLI

notifications targets seq list [<name>] [--serverUrl=<url>]

Option	Description
<name>	Filter by target name.
--serverUrl=<url>	Filter by Seq server URL.

Example

notifications targets seq list

Deleting a Seq target

Using the web interface

Open Administration > Notifications, select the Seq tab, select the target, and click Delete.

Using the CLI

notifications targets seq delete <name>

Option	Description
<name>	Name of the target to delete.

Example

notifications targets seq delete seq-replication

Slack

A Slack target posts notifications to a Slack channel through an incoming webhook.

Adding a Slack target

Using the web interface

1. Open Administration > Notifications, select the Slack tab, and click Add.
2. Under Name and Webhook Url, enter the channel's Webhook Url, and optionally a Name (defaults to Slack if left blank).
3. Under Modules Selection, choose All or specific categories.
4. Confirm to create the target.

Using the CLI

notifications targets slack add --webhookUrl=<text> [--minLevel=<name>] [--all | --modules=<name...>]
    [--batchPostingLimit=<numbers>] [--batchPostingPeriodInSec=<numbers>] [--name=<name>]

Option	Description
--webhookUrl=<text>	Slack incoming webhook URL.
--minLevel=<name>	Minimum event level to notify about. Defaults to Information.
--all	Notify about all categories. This is also what happens if you omit both --all and --modules.
--modules=<name...>	Specific category names to notify about.
--batchPostingLimit=<numbers>	The maximum number of events to post in a single batch. Must be greater than zero. If omitted, StorONE batches up to 100 events at a time.
--batchPostingPeriodInSec=<numbers>	How often (in seconds) StorONE checks for events to send. Must be greater than zero.
--name=<name>	Name for the target in StorONE (must be unique). Defaults to Slack.

Examples

Add a Slack target for a general alerts channel:

notifications targets slack add --webhookUrl https://hooks.slack.com/services/T00/B00/XXXXXXXX

Add a named Slack target that only posts Warning-and-above events for licensing and encryption:

notifications targets slack add --webhookUrl https://hooks.slack.com/services/T00/B01/YYYYYYYY --name slack-security --minLevel Warning --modules Licensing Encryption

Editing a Slack target

Using the web interface

1. Open Administration > Notifications, select the Slack tab, select the target, and click Edit.
2. Update the fields you need under Name and Webhook Url and Modules Selection.
3. Confirm the change.

Using the CLI

notifications targets slack edit <name> [--webhookUrl=<text>] [--minLevel=<name>] [--all | --modules=<name...>]
    [--batchPostingLimit=<numbers>] [--batchPostingPeriodInSec=<numbers>] [--newname=<name>]
    [--disableTarget | --enableTarget]

Option	Description
<name>	Name of the target to edit.
--webhookUrl=<text>	New Slack webhook URL.
--minLevel=<name>	Minimum event level to notify about.
--all	Notify about all categories.
--modules=<name...>	Specific category names to notify about.
--batchPostingLimit=<numbers>	The maximum number of events to post in a single batch. Must be greater than zero.
--batchPostingPeriodInSec=<numbers>	How often (in seconds) StorONE checks for events to send. Must be greater than zero.
--newname=<name>	New name for the target.
--disableTarget	Temporarily stop this target from receiving notifications.
--enableTarget	Re-enable a previously disabled target.

Example

notifications targets slack edit slack-security --webhookUrl https://hooks.slack.com/services/T00/B02/ZZZZZZZZ

Listing Slack targets

Using the web interface

Open Administration > Notifications and select the Slack tab.

Using the CLI

notifications targets slack list [<name>] [--webhookUrl=<text>]

Option	Description
<name>	Filter by target name.
--webhookUrl=<text>	Filter by Slack webhook URL.

Example

notifications targets slack list

Deleting a Slack target

Using the web interface

Open Administration > Notifications, select the Slack tab, select the target, and click Delete.

Using the CLI

notifications targets slack delete <name>

Option	Description
<name>	Name of the target to delete.

Example

notifications targets slack delete slack-security

Testing a notification target

Once you've configured a target, it's worth confirming it actually receives events before relying on it. The test command asks a specific StorONE node to generate a one-off notification with a severity, category, and message you choose, which is then dispatched to every matching target exactly as a real event would be.

Using the web interface

1. Open Administration > Notifications and choose Test Notification.
2. Under Nodes Selection, pick the Node that should generate the test event.
3. Choose the Level and Module, and enter a Message.
4. Confirm to send it.

Using the CLI

notifications test --node=<name> --level=<name> --module=<name> --message=<text> [--force]

Option	Description
--node=<name>	The S1 node that generates the test notification.
--level=<name>	Severity of the test notification.
--module=<name>	Category of the test notification.
--message=<text>	The message text.
--force	Skip the confirmation prompt shown when email settings haven't been configured yet (email targets simply won't receive the test in that case).

Examples

Send a test Warning-level Replication event from node s1-node-01:

notifications test --node s1-node-01 --level Warning --module Replication --message "Test notification from the docs"

Send a test Fatal-level event without confirmation prompts (useful in scripts):

notifications test --node s1-node-01 --level Fatal --module HighAvailability --message "Automated notification test" --force

---

Next: Browsing Notification History — searching the notifications StorONE has already generated.