Console.log(..) doesn't send anything to container's log after update to 1.15.2

Questions
1

Hello everyone!

Last week, we updated our n8n instance from version 0.223 to 1.15.2. Initially, everything seemed perfect, but today I encountered a peculiar issue. Typically, we send business event records to Splunk by using console.log() within a Code node (which then sends the output to the container’s stdout, and subsequently to Splunk).

However, post-upgrade, I’ve noticed that no records are appearing in Splunk, even though the workflows seem to be functioning normally without any errors. Does anyone have any insights or suggestions that could help us resolve this issue? Your assistance would be greatly appreciated. Thank you!

Information on your n8n setup

  • 1.15.2
  • Postgres
  • Docker
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

This was intentionally changed in 1.15.x because sending console.log output to stdout was never originally planned, was actually a bug and a potential compliance issue.
However, if you prefer to have this behavior, you can set CODE_ENABLE_STDOUT env variable to true.

2 Likes
4

@netroy Thank you so much! Is there any recommended way to send something to stdout from workflows? Or it is better to use other ways to log events from workflows?

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.