Home / Edge/ Reference·CLI Reference

CLI Reference

Command line interface basics and reference


In addition to starting and stopping the Cribl Edge server, the Cribl Edge command line interface enables you to initiate many configuration and administrative tasks directly from your terminal.

The command-line interface is only available to on-prem or hybrid customers.

To use the CLI:

  1. First check that you have read/write access to the directory where Cribl Edge is installed. Contact your Cribl administrator to request access if needed.

  2. Navigate to the directory where Cribl Edge is installed:

    cd $CRIBL_HOME/bin
  3. Execute a command. CLI commands have this basic syntax:

    ./cribl <command> <sub-command> <options> <arguments>

    Not all commands have sub-commands.

  4. To see the documentation for any command, append the --help option. For example:

    ./cribl vars --help
    
    ./cribl vars get --help
    
    ./cribl vars get -i myArray --help

Prevent and Troubleshoot CLI Problems

Immediate Execution

As indicated in the command reference and sample output, some commands take effect immediately.

Commands that require additional input will echo the sub-commands, options, and arguments they expect.

Persistent Volumes

If you start Cribl Edge with the CRIBL_VOLUME_DIR variable, all subsequent CLI commands should have this variable defined. Otherwise, those commands will apply the Cribl Edge default directories, yielding misleading results.

You can set CRIBL_VOLUME_DIR as an environment variable, or you can explicitly include it in each command, as in this example:

CRIBL_VOLUME_DIR=<writable-path-name> /opt/cribl/bin/cribl status

When set, $CRIBL_VOLUME_DIR overrides $CRIBL_HOME.

Avoid setting $CRIBL_VOLUME_DIR to an existing folder because it creates predefined folders in the specified directory. If that directory already contains folders with those names, Cribl Edge will overwrite those directories.

Failover Mode

In failover mode, set the CRIBL_CONF_DIR variable to your failover directory, ensuring your CLI commands access the correct configuration directory. For example, CRIBL_CONF_DIR=/<path_to_failover_volume> cribl diag create.

Your failover directory is either defined by the environment variable CRIBL_DIST_LEADER_FAILOVER_VOLUME (alternatively CRIBL_DIST_MASTER_FAILOVER_VOLUME), or defined in the instance.yml configuration file.

Commands Available

To see a list of available commands, enter ./cribl alone (or the equivalent ./cribl help). To execute a command, or to see its required parameters, enter ./cribl <command>.

CommandDescription
authCommand to log into or out of the product
boot-startCommand to enable or disable product boot-start
cloud-workspaceCommand to update a Leader with new config that allows it to connect to the Cribl.Cloud Leader and send it usage metrics
decryptCommand to decrypt data with a secret key
diagCommand to manage diagnostic bundles
encryptCommand to encrypt data with a secret key
gitCommand to manage Worker Group or Fleet configuration
helpDisplays a list of commands and their help
keysCommand to manage encryption keys
limitsCommand to control the availability of Cribl features
mode-masterCommand to configure an instance as a Leader
mode-singleCommand to configure an instance as a Single-instance deployment
mode-edgeCommand to configure Cribl Edge as a Single-instance deployment
mode-workerCommand to configure Cribl Stream as a Worker instance
mode-managed-edgeCommand to configure Cribl Edge as an Edge Node
ncCommand to listen a port for traffic and output stats and data
nodeCommand to execute a JavaScript file
packCommand to mange Cribl packs
parquetCommand to view a Parquet file, its metadata, or its schema
pipeCommand to feed stdin to a Pipeline
reloadCommand to reload the product
restartCommand to restart the product
scopeScope a Linux Command via AppScope
startCommand to start the product
statusCommand to display the product status
stopCommand to stop the product
varsCommand to manage global variables
versionCommand to display product version