System Settings Overview

Within the System Settings menu item, the platform modules with their parameters are presented.

They can be displayed in User or Expert mode. The latter can be activated by ticking the appropriate checkbox at the top right corner of the panel to get the full list of parameters.

jca system settings

The table of system settings provides information on the Names of modules and parameters they include, their Default and custom Values, Mode a particular parameter is available in (USER or EXPERT), Description with some parameters’ details and the date of Last change. 

In order to modify any setting, expand the list with required parameter (or find it via Search), select the one you need and click Edit. In the opened frame, specify a new value and confirm the change with the OK button.

edit system setting
After that, obligatory Apply the performed amendments with the same-named button. This will restart the needed component with new settings.

apply system settings changes

Cron Job Parameters for Scheduling Conditional System Actions

There is a special group of settings allowing to schedule some conditional system actions mainly connected with billing and statistics using cron jobs. In the table below you can find their description and default values.

Id

Module name

Parameter name

Parameter default value in cron expression format

Actual value in readable text format

Parameter description

1

jbilling

qjob.invoice.cron_schedule

0 0 0 1 * ?

At 00:00:00am, on the 1st day, every month

Creates invoices for the post users in accordance with consumed resources for the last month and process the payment of these invoices

2

jbilling

qjob.retry_pay_invoice.cron_schedule

0 0 * 1-10 * ?

At second :00 of minute :00 of every hour, every day between 1st and 10th, every month

Retries to process the payment of the the invoices that were not covered using the qjob.invoice.cron_schedule job

3

jbilling

qjob.stat_2_money.cron_schedule

0 15 * * * ?

At second :00 of minute :15 of every hour

Generates billing history based on the statistics that was collected by DumpStatisticTask and apps_options job.

And charges billing users based on the generated statistics

4

jbilling

qjob.retry_bill_apps.cron_schedule

0 20 * * * ?

At second :00 of minute :20 of every hour

Tries to recharge the environments that failed to be charged by Stat2Money

5

jbilling

qjob.retry_bill_accs.cron_schedule

0 40 * * * ?

At second :00 of minute :40 of every hour

Tries to recharge all accounts that failed to be charged by Stat2Money

6

jbilling

qjob.destroy_accs.cron_schedule

0 02 * * * ?

At second :00 of minute :02 of every hour

Destroys deactivated users

7

jbilling

qjob.deactive_accs.cron_schedule

0 35 * * * ?

At second :00 of minute :35 of every hour

Deactivates users when:

- their trial period is over

- if their bonus/trial balance is lower than account.trial.bonus quota

8

jbilling

qjob.notify_destroy_accs.cron_schedule

0 20 * * * ?

At second :00 of minute :20 of every hour

Notifies the user that the account will be destroyed soon

9

jbilling

qjob.predict_deactivation_accs.cron_schedule

0 15 * * * ?

At second :00 of minute :15 of every hour

Notifies the user about upcoming deactivation of the account

10

jbilling

qjob.threshold_notification.cron_schedule

0 15 * * * ?

At second :00 of minute :15 of every hour

Notifies billing users when their balance falls below the account.minbalance quota

11

jbilling

qjob.trial_end_notification.cron_schedule

0 15 * * * ?

At second :00 of minute :15 of every hour

Notifies the user about the end of the trial period

12

jbilling

qjob.account_statistic.cron_schedule

0 50 23 * * ?

At 23:50:00pm every day

Collects statistics by groups and accounts statuses

13

jbilling

qjob.invoice_checker.schedule

0 0 0/1 1/1 * ? *

At second :00, at minute :00, every hour starting at 00am, every day starting on the 1st, every month

Checks the status of invoices of the POST group users in PBA billing system

14

jbilling

qjob.stat_2_money_trial.cron_schedule

0 30 * * * ?

At second :00 of minute :30 of every hour

Generates billing history based on the statistics that was collected by DumpStatisticTask and apps_options jobs and charges trial users

15

jbilling

qjob.billing_history_aggregate.cron_schedule

0 0 0/1 * * ?

At second :00, at minute :00, every hour starting at 00am, of every day

Aggregates (24h => 1 day) billing history to reduce the load on the database

16

jbilling

qjob.autopay_level_balance_job.cron_schedule

0 20 * * * ?

At second :00 of minute :20 of every hour

Tries to make automatic payment through an external billing system based on the user's balance

17

jelastic

qjob.sleep_passive_apps_of_trials.cron_schedule

0 0 0 * * ?

At 00:00:00am every day

Hibernates environments based on their inactivity for the period stated in the sleep.after.inactive.hours quota

18

jelastic

qjob.container_population.cron_schedule

0 0 0/1 * * ?

At second :00, at minute :00, every hour starting at 00am, of every day

Collects statistics on the number of containers and their status

19

jelastic

qjob.apps_options.cron_schedule

0 0 0/1 * * ?

At second :00, at minute :00, every hour starting at 00am, of every day

Collects statistics on the usage of SSL, IPv4 and IPv6

20

jelastic

qjob.log_envs_population.cron_schedule

0 0 0/1 * * ?

At second :00, at minute :00, every hour starting at 00am, of every day

Collects statistics on the number of environments

21

jelastic

qjob.log_cluster_load.cron_schedule

0 0 0/4 * * ?

At second :00, at minute :00, every 4 hours starting at 00am, of every day

Collects statistics of the allocated RAM in percentage on the cluster

22

jelastic

qjob.delete_illegal_containers.cron_schedule

0 0 * * * ?

At second :00 of minute :00 of every hour

Removes containers which failed to be created or cloned

23

jelastic

qjob.hardnodes_load.cron_schedule

0 0/1 * * * ?

At second :00, every minute starting at minute :00, of every hour

Collects data about hardware nodes load

24

jelastic

qjob.sync_envs_state.cron_schedule

0 0/30 * * * ?

At second :00, every 30 minutes starting at minute :00, of every hour

Synchronizes the location and status of the environments.

Fixes “hanging” environments with one of the following statuses: LAUNCHING, STOPPING, GOING_TO_SLEEP, CREATING, CLONING

25

jelastic

qjob.dbquery_report.cron_schedule

0 0 0/1 * * ? 2025

At second :00, at minute :00, every hour starting at 00am, every day, in 2025

Collects custom reports (described in the system settings) and sends them to the stated email

26

jelastic

qjob.pcs_cluster_statistic.cron_schedule

0 0 0/1 * * ?

At second :00, at minute :00, every hour starting at 00am, of every day

Collects hardware node statistics for the PCS cluster

27

jelastic

qjob.templates_update.cron_schedule

0 0 0 * * ?

Close

At 00:00:00am every day

Checks if new tags are available for dockerized templates. Synchronizes tags available on the platform & Docker hub

28

jelastic

qjob.updater.cron_schedule

0 0 0/1 * * ? 2025

At second :00, at minute :00, every hour starting at 00am, every day, in 2025

Performs complex updates, currently used for updating old containers with new firewall rules

29

jelastic

qjob.ssl_checker.cron_schedule

0 0 15 * * ?

At 15:00:00pm every day

Checks the status of Let’s Encrypt SSL certificate for platform domain and automatically prolongs it if needed. Available since 5.4.5

30

statistic

DumpStatisticTask

At the beginning of every hour (Hard coded)


Aggregates the collected statistics for each resource type on hourly basis

31

statistic

CollectStatisticTask

Every 20/60 seconds for LINUX / WIN hard nodes


Collects current statistics for displaying in the dashboard and for the further aggregation by DumpStatisticTask job


You can customize the parameters in accordance with your requirements. Note that the values are stored in cron expression format. Follow the link to find out more about this format and how to convert it to readable text.