Logs
After executing a flow, you can review detailed logs for both the overall flow run and individual components. These logs help you trace how data moves through the flow, including the Message objects received or produced by input and output components.
Configure log options
Use Robility flow environment variables to configure logging options in your Robility flow .env file, and then start Robility flow with uv run Robility flow run –env-file .env.
The following environment variables are available to configure logging:
1. ROBILITY FLOW_LOG_LEVEL: Sets the log level as one of DEBUG, ERROR (default), INFO, WARNING, and CRITICAL. For example, ROBILITY FLOW_LOG_LEVEL=DEBUG.
2. ROBILITY FLOW_LOG_FILE: Sets the log file storage location if you want to use a non-default location. For example, ROBILITY FLOW_LOG_FILE=path/to/logfile.log
3. ROBILITY FLOW_LOG_ENV: Controls log output and formatting.
a. ROBILITY FLOW_LOG_ENV=container: Outputs serialized JSON to stdout.
b. ROBILITY FLOW_LOG_ENV=container_csv: Outputs CSV-formatted plain text to stdout.
c. ROBILITY FLOW_LOG_ENV=default or unset: Outputs prettified output with RichHandler.
4. ROBILITY FLOW_LOG_ROTATION controls when the log file is rotated, either based on time or file size. By default, logs are rotated every 1 day.
a. Time-based rotation: “1 day”, “12 hours”, “1 week”
b. Size-based rotation: “10 MB”, “1 GB”
c. Disable rotation: “None” (log files will grow without limit)
Flow and component logs
After you run a flow, you can inspect the logs for each component and flow run. For example, you can inspect Message objects ingested and generated by Input and Output components.
Viewing Flow Logs
To view logs for the entire flow:
a. Open the flow in the visual editor.
b. Click Logs in the top menu to access the complete execution log.
This provides a consolidated view of the flow’s behavior during runtime, useful for debugging and analysis.
To examine data flowing through your components:
1. In the Logs view, click the cells under the Inputs or Outputs columns for a specific component.
2. This opens the corresponding Message object or raw output data.
Example: Message Object from a Chat Input Component
json
CopyEdit
“messages”: [
{
“message”: “What’s the recommended way to install Docker on Mac M1?”,
“sender”: “User”,
“sender_name”: “User”,
“session_id”: “Session Apr 21, 17:37:04”,
“stream_url”: null,
“component_id”: “ChatInput-4WKag”,
“files”: [],
“type”: “text”
}
]
Input and output components may not always work with Message objects directly. For example, a Language Model might return plain text, which is then wrapped into a Message object by a downstream Chat Output component.
Viewing Chat Logs
To inspect chat interactions:
a. Open the Playground and select a session.
b. View the complete chat history, including messages sent, responses generated, and system-level interactions.
For more details, see View Chat History.
Viewing Output from a Specific Component
If you’re troubleshooting incorrect or malformed flow outputs:
a. In the visual editor, locate the component.
b. Click Inspect Output to view the data it produced during the latest run.
This helps isolate issues and verify how data is transformed at each step of the flow.
