workspace
A Tailpipe workspace is a "profile" that provides a distinct filesystem location for your collected logs and allows you to define options for running Tailpipe.
You can use workspaces to keep independent sets of data. Each workspace maintains its own data files written to $TAILPIPE_INSTALL_DIR/data/{workspace name} (e.g. ~/.tailpipe/data/default).
Tailpipe workspaces allow you to define multiple named configurations and easily switch between them using the --workspace argument or TAILPIPE_WORKSPACE environment variable.
Arguments
| Argument | Default | Description |
|---|---|---|
| log_level | off | Set the logging output level |
| update_check | true | Enable or disable automatic update checking. |
| memory_max_mb | 0 (unlimited) | Caps CLI memory usage and determines worker count. |
| plugin_memory_max_mb | 0 (unlimited) | Sets soft memory cap per plugin. |
| temp_dir_max_mb | 0 (unlimited) | Limits JSONL temp file size on disk. |
Workspaces are defined using the workspace block in one or more Tailpipe config files. You can define them in any configuration file (*.tpc) from your config directory (~/.tailpipe/config by default), but by convention, they are usually written to ~/.tailpipe/config/workspaces.tpc.
The workspace named default is special; If a workspace named default exists, it will be used whenever the --workspace argument is not passed to Tailpipe. Creating a default workspace in ~/.tailpipe/config/workspaces.tpc provides a way to set all defaults.
Note that the HCL arguments correspond to environment variables:
| Workspace Argument | Environment Variable |
|---|---|
| log_level | TAILPIPE_LOG_LEVEL |
| update_check | TAILPIPE_UPDATE_CHECK |
| memory_max_mb | TAILPIPE_MEMORY_MAX_MB |
| plugin_memory_max_mb | TAILPIPE_PLUGIN_MEMORY_MAX_MB |
| temp_dir_max_mb | TAILPIPE_TEMP_DIR_MAX_MB |