Any custom Advanced Features configurations - such as Datamodels, Bloks, Alert Triggers, Smart Lists, Dashboards, Aggregation Rules, Trigger Groups - can be backed - up to get imported into another system or to restore missing custom configurations.

Exporting Configurations

Administrators can easily save all custom Advanced Features configuration to a default JSON file (loguconfig.json) with below command:
 
# /loglogic/logu/configurator/bin/llconf export
 
Other available options is to export the Advanced Features configurations to a YAML or ZIP file. The default name will be loguconfig.yml or loguconfig.zip depending of the flag used. I.e:
 
# /loglogic/logu/configurator/bin/llconf export -y
 
The above is to export configurations to a YAML file. To export the configurations to a ZIP file use '-z':
 
# /loglogic/logu/configurator/bin/llconf export -z
 
Additionally, we can specify a file to store the dumped configurations by using the '-f' flag:
 
# /loglogic/logu/configurator/bin/llconf export -f /loglogic/tmp/myCustomConf.json
 
Furthermore, Administrators can export one or more specific custom configurations. To do so, we need to create a JSON file specifying the custom advanced configurations we wish to export/backup. Such a file should look like:
 
{
 "sources" : [ "MyDatamodel2", "MyDatamodel3" ],   // This will export Data Models named "abc" and "xyz" only
 "bloks" : ["MS*"],            // Export all Blok configurations with name starting "blok"
 "alertTriggers" : ["*"],        // Export all triggers
 "smartlists" : ["*"],           // Export all Smartlist configurations
 "dashboards" : ["*"],           // Export all Dashboard configurations
 "aggrRules":["*"],              // Export all aggregation rules
 "triggerGroups":["*"]           // Export all trigger groups
}
 
In below example we will export a single Datamodel named "MyDatamodel5". The 'configlist' file should looks like:
 
{
"sources" : [ "MyDatamodel5" ]
}
 
Given a configlist file that is named like 'exportSingleDM.json', the command to export the Datamodel should be:
 

# /loglogic/logu/configurator/bin/llconf export --configlist /loglogic/support/exportSingleDM.json -f /loglogic/support/exportedForm_154.json

 
To export more than one custom Datamodel we can  specify them separated by ','. I.e:
 
{
"sources" : [ "MyDatamodel3", "MyDatamodel5" ]
}

Exporting groups:

To export a JSON file with only the groups structure:
  

# /loglogic/logu/configurator/bin/llconf export -f logu.json --verbose --groupsOnly    

Entities other than groups are not exported.

Administrators can use the same procedure as above to export bloks, alertTriggers, smatlists, dashboards, aggrRules, triggerGroups.

Importing Configurations

To import all configurations:
 

# /loglogic/logu/configurator/bin/llconf import

# /loglogic/logu/configurator/bin/llconf import -f <path_to_file>

Keep in mind that spaces in the file name or path are not supported.

# /loglogic/logu/configurator/bin/llconf import -o

This article explains how to export specific custom Advance Features configurations