Component console output is not visible when registry uses remote storage

[leandrowilliam]

Problem

When running the OC registry with remote storage, component console output (logs from console.log, console.error, etc.) is not visible in the logs. This makes it difficult to debug components in lower environments and production.

In contrast, when running locally with oc dev command, component logs are visible on the console.

Current Behavior

• ✅ Local development (oc dev): Component logs are visible
• ❌ Remote storage: Component logs are silently discarded

Expected Behavior

• Component logs should be visible regardless of where the components are served from (local filesystem or remote storage)
• Registry administrators should be able to control component logging for debugging purposes in any environment

Impact

Developers cannot debug component behavior in lower environments and production, making it harder to troubleshoot issues that only appear in those environments.

[leandrowilliam]

Hi @ricardo-devis-agullo, I just wanted to check if there’s any update on this PR/issue when you have a chance. Thanks!

[leandrowilliam]

Hi @ricardo-devis-agullo, I just wanted to check if there’s any update on this PR/issue when you have a chance. Thanks!

By the way, I was looking at the code again regarding the distinction you mentioned for ‘local’, and I think the implementation actually aligns with what you described (which would mean this PR might not be necessary).
I think my confusion came from the documentation instead.

What do you think we should do then? Should we close this issue and update the docs instead? Using local: true seems to solve my use case locally.

That said, I do see potential future use cases for enabling some form of logging in non-local environments. Curious to hear your thoughts.

[ricardo-devis-agullo]

I'll ammend that documentation since that is not really true. local=true is just something that is passed when running oc dev. It doesn't just switch to local file system, among other things it will also disable the ability to publish components (since in local you dont have that need)

[leandrowilliam]

I'll ammend that documentation since that is not really true. local=true is just something that is passed when running oc dev. It doesn't just switch to local file system, among other things it will also disable the ability to publish components (since in local you dont have that need)

Yep, you’re right. I just tried local: true in a lower environment and it didn’t work. So I think it makes sense to move forward with the componentConsole idea you proposed

[leandrowilliam]

@ricardo-devis-agullo Hi, do you have any updates on this one? Thanks