From ea0c49dbb395730bba31b185473acfc9a5322cf3 Mon Sep 17 00:00:00 2001 From: riddhi2910 Date: Tue, 10 Mar 2026 11:34:49 -0700 Subject: [PATCH 1/8] Update logging.md --- .../app_builder_guides/application_logging/logging.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/src/pages/guides/app_builder_guides/application_logging/logging.md b/src/pages/guides/app_builder_guides/application_logging/logging.md index 2b163a4d1..305a88c9e 100644 --- a/src/pages/guides/app_builder_guides/application_logging/logging.md +++ b/src/pages/guides/app_builder_guides/application_logging/logging.md @@ -30,6 +30,16 @@ Both the core logging library and the core errors library can be used directly i When a new App Builder application is bootstrapped from the [AIO CLI](https://github.com/adobe/aio-cli) using the `aio app init` command, the [generated boilerplate action code](https://github.com/adobe/generator-aio-app) integrates with both the core and errors logging libraries by default. +### Log Level (LOG_LEVEL) and What Gets Written + +You control which log levels are emitted by setting the `LOG_LEVEL` input (for example in your action's `inputs` in `manifest.yml` or `app.config.yaml`). The runtime filters logs by this level before writing: only messages at or above the configured level are written. For example: + +- If `LOG_LEVEL` is `error`, only `logger.error()` output is written (and typically goes to stderr). Calls to `logger.info()`, `logger.debug()`, and `logger.warn()` are not written at all, so they never appear in the Logs UI or CLI. +- If `LOG_LEVEL` is `info`, you get `info`, `warn`, and `error`; `logger.debug()` is not written. +- If `LOG_LEVEL` is `debug`, all levels are written. + +If you do not see expected `logger.info()` or `logger.debug()` output in the Logs UI or CLI, ensure the action's `LOG_LEVEL` is set to `info` or `debug` (for example `LOG_LEVEL: debug` in the action inputs). The Logs UI filters by stream (stdout or stderr); what appears in each stream depends on what was actually emitted, which is governed by `LOG_LEVEL`. + ## Accessing logs with App Builder CLI App Builder [CLI](https://github.com/adobe/aio-cli) exposes application logs to Developers at different levels: @@ -79,6 +89,7 @@ The Logs UI displays logs from all your Runtime action activations, including bo - The full action path (e.g., `mynamespace/mypackage/myaction`) - A short action name (e.g., `myaction`) - **Free-text search**: Search within log messages for specific content such as error messages, log levels (`info`, `error`, `warn`), or any text present in your logs +- **Log stream filter**: Filter by output stream (All, stdout, or stderr). What appears in each stream depends on what your action wrote and on the action's `LOG_LEVEL` (see [Log Level (LOG_LEVEL) and What Gets Written](#log-level-log_level-and-what-gets-written)). ### When to use the Console UI From 467d7e95e54ed5831a5a2f5532c4f382c321f40b Mon Sep 17 00:00:00 2001 From: riddhi2910 Date: Tue, 10 Mar 2026 11:49:09 -0700 Subject: [PATCH 2/8] Fix the lint error --- .../app_builder_guides/configuration/webpack-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md b/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md index 293357bc8..9d3b7cbcb 100644 --- a/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md +++ b/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md @@ -142,7 +142,7 @@ Assuming that `config` contains your Webpack configuration: }, target: 'node' // Cannot change entry: [ - '', + '\', ...config.entry ], resolve: { From ca09c0433c6c3508dc8de0fce361590a91684904 Mon Sep 17 00:00:00 2001 From: Riddhi Prajapati <32148809+riddhi2910@users.noreply.github.com> Date: Tue, 10 Mar 2026 13:25:58 -0700 Subject: [PATCH 3/8] fix a line --- .../guides/app_builder_guides/application_logging/logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/guides/app_builder_guides/application_logging/logging.md b/src/pages/guides/app_builder_guides/application_logging/logging.md index 305a88c9e..aa4e587d0 100644 --- a/src/pages/guides/app_builder_guides/application_logging/logging.md +++ b/src/pages/guides/app_builder_guides/application_logging/logging.md @@ -34,7 +34,7 @@ When a new App Builder application is bootstrapped from the [AIO CLI](https://gi You control which log levels are emitted by setting the `LOG_LEVEL` input (for example in your action's `inputs` in `manifest.yml` or `app.config.yaml`). The runtime filters logs by this level before writing: only messages at or above the configured level are written. For example: -- If `LOG_LEVEL` is `error`, only `logger.error()` output is written (and typically goes to stderr). Calls to `logger.info()`, `logger.debug()`, and `logger.warn()` are not written at all, so they never appear in the Logs UI or CLI. +- If `LOG_LEVEL` is `error`, only `logger.error()` output is written, goes to stdout. Calls to `logger.info()`, `logger.debug()`, and `logger.warn()` are not written at all, so they never appear in the Logs UI or CLI. - If `LOG_LEVEL` is `info`, you get `info`, `warn`, and `error`; `logger.debug()` is not written. - If `LOG_LEVEL` is `debug`, all levels are written. From c38f05239563ff4b25439c0bcc1e2d4a427b3f5e Mon Sep 17 00:00:00 2001 From: riddhi2910 Date: Tue, 10 Mar 2026 14:46:02 -0700 Subject: [PATCH 4/8] Fix the log doc --- .../app_builder_guides/application_logging/logging.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/pages/guides/app_builder_guides/application_logging/logging.md b/src/pages/guides/app_builder_guides/application_logging/logging.md index 305a88c9e..f693f781f 100644 --- a/src/pages/guides/app_builder_guides/application_logging/logging.md +++ b/src/pages/guides/app_builder_guides/application_logging/logging.md @@ -34,11 +34,11 @@ When a new App Builder application is bootstrapped from the [AIO CLI](https://gi You control which log levels are emitted by setting the `LOG_LEVEL` input (for example in your action's `inputs` in `manifest.yml` or `app.config.yaml`). The runtime filters logs by this level before writing: only messages at or above the configured level are written. For example: -- If `LOG_LEVEL` is `error`, only `logger.error()` output is written (and typically goes to stderr). Calls to `logger.info()`, `logger.debug()`, and `logger.warn()` are not written at all, so they never appear in the Logs UI or CLI. +- If `LOG_LEVEL` is `error`, only `logger.error()` output is written. Calls to `logger.info()`, `logger.debug()`, and `logger.warn()` are not written at all, so they never appear in the Logs UI or CLI. - If `LOG_LEVEL` is `info`, you get `info`, `warn`, and `error`; `logger.debug()` is not written. - If `LOG_LEVEL` is `debug`, all levels are written. -If you do not see expected `logger.info()` or `logger.debug()` output in the Logs UI or CLI, ensure the action's `LOG_LEVEL` is set to `info` or `debug` (for example `LOG_LEVEL: debug` in the action inputs). The Logs UI filters by stream (stdout or stderr); what appears in each stream depends on what was actually emitted, which is governed by `LOG_LEVEL`. +If you do not see expected `logger.info()` or `logger.debug()` output in the Logs UI or CLI, ensure the action's `LOG_LEVEL` is set to `info` or `debug` (for example `LOG_LEVEL: debug` in the action inputs). ## Accessing logs with App Builder CLI @@ -89,7 +89,7 @@ The Logs UI displays logs from all your Runtime action activations, including bo - The full action path (e.g., `mynamespace/mypackage/myaction`) - A short action name (e.g., `myaction`) - **Free-text search**: Search within log messages for specific content such as error messages, log levels (`info`, `error`, `warn`), or any text present in your logs -- **Log stream filter**: Filter by output stream (All, stdout, or stderr). What appears in each stream depends on what your action wrote and on the action's `LOG_LEVEL` (see [Log Level (LOG_LEVEL) and What Gets Written](#log-level-log_level-and-what-gets-written)). +- **Log stream filter**: Filter by stream (All, stdout, or stderr). `LOG_LEVEL` controls which `logger.*()` messages are emitted, but the App Builder SDK writes all logger output to stdout by default (including `logger.error()`). stderr typically contains uncaught exceptions and `console.error()`. ### When to use the Console UI From 50e3e77d1d9fd05b7f4d262b29640d2651a4f9ef Mon Sep 17 00:00:00 2001 From: Riddhi Prajapati <32148809+riddhi2910@users.noreply.github.com> Date: Wed, 11 Mar 2026 11:25:50 -0700 Subject: [PATCH 5/8] Fix --- .../guides/app_builder_guides/application_logging/logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/guides/app_builder_guides/application_logging/logging.md b/src/pages/guides/app_builder_guides/application_logging/logging.md index 6aea84577..256e732ca 100644 --- a/src/pages/guides/app_builder_guides/application_logging/logging.md +++ b/src/pages/guides/app_builder_guides/application_logging/logging.md @@ -65,7 +65,7 @@ The AIO CLI [Runtime plugin](https://github.com/adobe/aio-cli-plugin-runtime) op This command also offers options to `--watch` or `--tail` the logs, and other options you can review by running `aio runtime logs --help`. -As with `aio app logs`, the `aio runtime logs` command can be used by Developers or by scripts running in a [CI/CD pipeline](../deployment/cicd-for-app-builder-apps.md). The command can also be used for App Builder applications deployed on Runtime or running locally through the `aio app run --local` command as discussed in the [Deployment Guide](../deployment/deployment.md). +As with `aio app logs`, the `aio runtime logs` command can be used by Developers or by scripts running in a [CI/CD pipeline](../deployment/cicd-for-app-builder-apps.md). The command can also be used for App Builder applications deployed on Runtime or running locally through the `aio app dev || aio app run` command as discussed in the [Deployment Guide](../deployment/deployment.md). ## Viewing logs in Adobe Developer Console From effaddb5c5535e7d0ccef8af52f12b7a9c104d06 Mon Sep 17 00:00:00 2001 From: Riddhi Prajapati <32148809+riddhi2910@users.noreply.github.com> Date: Wed, 11 Mar 2026 11:31:46 -0700 Subject: [PATCH 6/8] Update webpack-configuration.md --- .../app_builder_guides/configuration/webpack-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md b/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md index 9d3b7cbcb..293357bc8 100644 --- a/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md +++ b/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md @@ -142,7 +142,7 @@ Assuming that `config` contains your Webpack configuration: }, target: 'node' // Cannot change entry: [ - '\', + '', ...config.entry ], resolve: { From 8afea87ede19a7a1dc5d29f6887746d37de3404a Mon Sep 17 00:00:00 2001 From: Riddhi Prajapati <32148809+riddhi2910@users.noreply.github.com> Date: Wed, 11 Mar 2026 12:12:33 -0700 Subject: [PATCH 7/8] Update webpack-configuration.md --- .../app_builder_guides/configuration/webpack-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md b/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md index 293357bc8..9ff26789f 100644 --- a/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md +++ b/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md @@ -142,7 +142,7 @@ Assuming that `config` contains your Webpack configuration: }, target: 'node' // Cannot change entry: [ - '', + '\', ...config.entry ], resolve: { From efb49cd8411d12229c03c07a0510108c4f039414 Mon Sep 17 00:00:00 2001 From: Riddhi Prajapati <32148809+riddhi2910@users.noreply.github.com> Date: Wed, 11 Mar 2026 12:22:45 -0700 Subject: [PATCH 8/8] Update webpack-configuration.md --- .../app_builder_guides/configuration/webpack-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md b/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md index 9ff26789f..e6fcd4924 100644 --- a/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md +++ b/src/pages/guides/app_builder_guides/configuration/webpack-configuration.md @@ -142,7 +142,7 @@ Assuming that `config` contains your Webpack configuration: }, target: 'node' // Cannot change entry: [ - '\', + 'path to the action', ...config.entry ], resolve: {