Notification Settings

The platform notification system contains a set of emails which can be divided into the following categories:

• common
• beta
• trial
• billing
• system

• Common emails
  Common emails are the notifications about such events as creating environment, adding node or add-on, resetting password, changing the status of the account and warnings about lack of resources. They are used for all types of user accounts and sent by default when any mentioned event happens. You need to configure just the notifications about lack of resources (RAM and CPU).

• Beta emails
  Beta emails contain just two specific notifications: welcome email and notification about the end of the beta period. The first email is sent automatically after registration of a new beta user, and the second one is sent manually right after commercial launch to all beta users.

• Trial emails
  Trial emails are the notification about the registration, the completion of the trial period and the deletion of the deactivated account. To configure sending trial emails and the periodicity of these notifications:

  • Navigate to JCA > System settings.
  • Expand jbilling parameters.
  • Configure the following parameters:
    • account.trial.send.notification Enable notification of trial users about their account deactivation and destroy by setting the value to “1”. To disable them state “0”.
    • account.notification.periods Set the period (in days) when a trial user receives a notification about upcoming expiration of the trial period. Example: “1;3;6” value means that a user will get the notification in 6, 3 and 1 day before the end of the trial period.
    • qjob.trial_end_notification.cron_schedule Set this job schedule to notify your users in advance about the end of their trial period and necessity to convert the account. Example: qjob.trial_end_notification.cron_schedule=0 15 * * * ?
    • account.trial.destroy.notification.periods Set the period (in days) when a trial user receives a notification that the account is going to be destroyed. Example: “3;6” value means that a user will get the notification in 6 and 3 days before destroy.
    • Click the Apply button to make the settings available on production.

• Billing emails
  Billing emails are the notifications about the conversion to the billing group, the necessity to refill the account, deactivation and deletion of the account. To configure sending billing emails and the period of these notifications:

  • Navigate to JCA > System settings.
  • Expand jbilling parameters.
  • Configure the following parameters:
    • account.send.notification Enable notification of billing users about their account deactivation and destroy by setting the value to “1”. To disable them state “0”.
    • account.notification.periods Set the period (in days) when a billing user receives a notification that the credit is going to be consumed. Example: “1;3;6” value means that a user will get the notification in 6, 3 and 1 day before the balance is going to run out of money.
    • qjob.threshold_notification.cron_schedule Set this job schedule to notify your users about crossing a critical mark of the balance stated by the user. This setting does not configure schedule of the deactivation process itself. It only sets the notification schedule. Example: qjob.threshold_notification.cron_schedule=0 15 * * * ?
    • qjob.predict_deactivation_accs.cron_schedule This job schedule is configured to warn your users about coming deactivation of the account due to a low balance. Example: qjob.predict_deactivation_accs.cron_schedule=0 15 * * * ?
    • qjob.notify_destroy_accs.cron_schedule Set this job schedule to warn your users in advance about coming account destroy. Example: qjob.notify_destroy_accs.cron_schedule=0 20 * * * ?
    • account.destroy.notification.periods Set the period (in days) when a billing user receives a notification that the account is going to be destroyed. Example: “30;60” value means that a user will get the notification in 60 and 30 days before destroy.
  • Click the Apply button to make the settings available on production.

• System emails
  System emails are the internal notifications which are sent to the cluster administrator in order to inform about certain events in the platform system (statistics collection, pool regeneration, user billing, warnings about lack of disk resources). You need to configure just the notifications about lack of disk resources (disk space, i/o limits).