How to check logs in Langflow 1.3.2 when flows or components are running?

[shlim33]

I'm using Langflow 1.3.2. Logs are properly recorded in the console and log files when the server starts, but no logs are recorded when running flows or components. Could you please tell me how to check the logs?

[dosubot[bot]]

Hello @shlim33! I'm here to help you with your questions and issues while you wait for a human maintainer. If you have any bugs to fix or need assistance, just let me know!

To check logs in Langflow 1.3.2 when flows or components are running, you can access the Logs pane, which provides a detailed record of all component executions within a workspace. To access the Logs pane, click your Flow Name, and then select Logs.

Additionally, Langflow stores logs at the location specified in the LANGFLOW_CONFIG_DIR environment variable. You can modify the location of your log file by adding LANGFLOW_LOG_FILE=path/to/logfile.log in your .env file and starting Langflow with uv run langflow run --env-file .env.

For real-time log streaming, you can use Server-Sent Events (SSE) by executing the following command:

curl -X GET \
  "$LANGFLOW_URL/logs-stream" \
  -H "accept: text/event-stream"

This will allow you to stream logs as they are generated during flow or component execution. Additionally, you can retrieve logs with optional query parameters such as lines_before, lines_after, and timestamp to customize the log retrieval:

curl -X GET \
  "$LANGFLOW_URL/logs?lines_before=0&lines_after=0&timestamp=0" \
  -H "accept: application/json"

This command will return the last 10 lines of logs by default.

To ensure logs appear in the component output logs tab, you need to explicitly call self.log() in your component code. For example, adding self.log('xxx', 'xxx') to your component code will output logs that appear in the logs tab. By default, most components don't output logs unless they specifically implement this logging call, though some components like the Agent Component do include logging by default ^[1][2][3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}