Alerts let you configure some pre-defined actions that will generate an email to you alerting to you of what is going on. One example is a reminder when the server isn't up to date for a new release of CrushFTP. Or a notice when a drive is getting low on disk space, or anytime a user changes their password or gets low on quota space...you want to know.

Alerts are global, where the user events are specific to a particular user and event type.

You can configure predefined alerts choosing from the dropdown list.

You can also have preconfigured Crushtask plugins that you can trigger from the alert config.

One useful alert item is the catch invalid email attempts. This is useful if you send out automated emails based on user input for example on an upload. If they type the email wrong, no one would know the email was never delivered. You can do an email like this in the event to handle this (the variables will be filled in with the emails contents):

From:{from}
To:{to}
CC:{cc}
BCC:{bcc}
Subject:{subject}
Error{result}

{body}

Some other special alerts can be configured under the Admin > Preferences > Email Templates where you can configure the below alerts so you get notified of changes done on the CrushFTP settings, or on the users. You will need to have at least CrushFTP 8.2.1._47 for these to work. Since these are email templates, use the CC to enter the email address you want to receive the emails.

If this is created, then admins changing things on CrushFTP settings, will cause alert emails out to whatever is configured on the email template.

If this is created, then admins changing things on CrushFTP user config, will cause alert emails out to whatever is configured on the email template.

If this is created, then admins changing things will cause alert emails out to the original user, and new user if their email is changed.

If you have configured the max run time for a job another useful alert to be configured is the one that send emails in case of the max run time was reached so you can know that the job is stuck at some point.

Example alert for bad login (Enterprise-only):

After Version 10.0.0 Build: 32 the Alerts feature allows distinguishing the failed login due to a bad password from the failed login due to inexisting username. In Preferences -> Alerts page we are configuring a Security alert not to send an email, but to run a plugin: a job that is built from Jump tasks and Email tasks.

In the Jump task we are inspecting whether the {alert_msg} variable contains "does exist" or "does not exist" expressions. If the username "does not exist", we send an email about that with a body like this: User {user_name} from the IP {user_ip} got rejected by the server. The user doesn't exist. If the username "does exist", the problem is the password. We send an email with a body like this: User {user_name} from the IP {user_ip} got rejected by the server due to an incorrect password or protocol.