File Logger

Node ID: logger · Role: Sink · Realtime config: no

Description

Records sensor data to JSON line files with configurable file rotation. Supports all data types and filtering by data type.

Inputs / Outputs

Inputs: (none)
Outputs: (none)

Config aliases

FileLogger, fileLogger, logger

Properties

Each row shows the setting’s label in the node’s Properties panel and, in code, its key in the node’s settings object in the config file. A setting omitted from the config file uses the default shown here.

Property	Type	Default	Description
File Path `filePath`	filepath_save	`log.json`	Relative paths are resolved against the user log directory (%LOCALAPPDATA%\FusionHub\logs on Windows, ~/.local/share/fusionhub/logs on Linux). Use an absolute path to write elsewhere.
Append date/time to filename `appendTimestamp`	boolean	`true`	Each recording session writes to a new file with a -MMDDYYYY-HHMM suffix inserted before the extension, so successive recordings don’t overwrite each other.
Start recording on engine start `autoStart`	boolean	`false`	When enabled, recording begins automatically as soon as the engine starts (useful for headless / batch runs). When disabled (default), recording must be triggered explicitly via the Start Recording button or the `startLogging` command.

Example node definition

A minimal entry in config.json looks like the block below. Paste it under the sinks key, keyed by an instance name of your choice. All settings are optional: anything not listed under settings uses the default from the Properties table above. See The configuration file for how the sections and endpoint wiring work.

{
  "sinks": {
    "logger": {
      "inputEndpoints": [],
      "settings": {}
    }
  }
}

Loading documentation…