[9.1] [scout] support log level override (#228841)#229557
Merged
dmlemeshko merged 1 commit intoelastic:9.1from Jul 28, 2025
Merged
[9.1] [scout] support log level override (#228841)#229557dmlemeshko merged 1 commit intoelastic:9.1from
dmlemeshko merged 1 commit intoelastic:9.1from
Conversation
## Summary - default log level for Playwright fixtures is `info` , afaik default for FTR and other scripts (but for now to better understand performance issues we pass `debug` through `node scripts/scout`, to be reverted for GA) - `node scripts/scout` will propagate log level from cli flag (e.g. --debug) with `SCOUT_LOG_LEVEL` env variable to playwright exec command - since some Team may not use `scripts/scout` command, they can set `LOG_LEVEL` variable to override to whatever level is needed if both `LOG_LEVEL` and `SCOUT_LOG_LEVEL` are set, the later has priority (important for us, shouldn't block others) ### Playwright Integration: * Replaced the use of `getLogger` with the updated `ScoutLogger` call in Playwright worker fixtures, enabling log level configuration via environment variables. * Modified the Playwright test runner to propagate the log level to the test environment using the `SCOUT_LOG_LEVEL` variable. --------- Co-authored-by: David Olaru <dolaru@vaevixen.com> (cherry picked from commit d76a5be) # Conflicts: # src/platform/packages/shared/kbn-scout/src/playwright/global_hooks/synthtrace_ingestion.ts
Contributor
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
|
csr
approved these changes
Jul 28, 2025
dmlemeshko
added a commit
that referenced
this pull request
Aug 4, 2025
# Backport This will backport the following commits from `main` to `8.19`: - [[scout] support log level override (#228841)](#228841) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-07-22T20:25:49Z","message":"[scout] support log level override (#228841)\n\n## Summary\n\n- default log level for Playwright fixtures is `info` , afaik default\nfor FTR and other scripts (but for now to better understand performance\nissues we pass `debug` through `node scripts/scout`, to be reverted for\nGA)\n- `node scripts/scout` will propagate log level from cli flag (e.g.\n--debug) with `SCOUT_LOG_LEVEL` env variable to playwright exec command\n- since some Team may not use `scripts/scout` command, they can set\n`LOG_LEVEL` variable to override to whatever level is needed\nif both `LOG_LEVEL` and `SCOUT_LOG_LEVEL` are set, the later has\npriority (important for us, shouldn't block others)\n\n### Playwright Integration:\n* Replaced the use of `getLogger` with the updated `ScoutLogger` call in\nPlaywright worker fixtures, enabling log level configuration via\nenvironment variables.\n* Modified the Playwright test runner to propagate the log level to the\ntest environment using the `SCOUT_LOG_LEVEL` variable.\n\n---------\n\nCo-authored-by: David Olaru <dolaru@vaevixen.com>","sha":"d76a5befa5ec73425b44c10b24f66a19556a7e83","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v8.19.0","ci:scout-ui-tests","v9.2.0","v9.1.1"],"title":"[scout] support log level override","number":228841,"url":"https://github.com/elastic/kibana/pull/228841","mergeCommit":{"message":"[scout] support log level override (#228841)\n\n## Summary\n\n- default log level for Playwright fixtures is `info` , afaik default\nfor FTR and other scripts (but for now to better understand performance\nissues we pass `debug` through `node scripts/scout`, to be reverted for\nGA)\n- `node scripts/scout` will propagate log level from cli flag (e.g.\n--debug) with `SCOUT_LOG_LEVEL` env variable to playwright exec command\n- since some Team may not use `scripts/scout` command, they can set\n`LOG_LEVEL` variable to override to whatever level is needed\nif both `LOG_LEVEL` and `SCOUT_LOG_LEVEL` are set, the later has\npriority (important for us, shouldn't block others)\n\n### Playwright Integration:\n* Replaced the use of `getLogger` with the updated `ScoutLogger` call in\nPlaywright worker fixtures, enabling log level configuration via\nenvironment variables.\n* Modified the Playwright test runner to propagate the log level to the\ntest environment using the `SCOUT_LOG_LEVEL` variable.\n\n---------\n\nCo-authored-by: David Olaru <dolaru@vaevixen.com>","sha":"d76a5befa5ec73425b44c10b24f66a19556a7e83"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/228841","number":228841,"mergeCommit":{"message":"[scout] support log level override (#228841)\n\n## Summary\n\n- default log level for Playwright fixtures is `info` , afaik default\nfor FTR and other scripts (but for now to better understand performance\nissues we pass `debug` through `node scripts/scout`, to be reverted for\nGA)\n- `node scripts/scout` will propagate log level from cli flag (e.g.\n--debug) with `SCOUT_LOG_LEVEL` env variable to playwright exec command\n- since some Team may not use `scripts/scout` command, they can set\n`LOG_LEVEL` variable to override to whatever level is needed\nif both `LOG_LEVEL` and `SCOUT_LOG_LEVEL` are set, the later has\npriority (important for us, shouldn't block others)\n\n### Playwright Integration:\n* Replaced the use of `getLogger` with the updated `ScoutLogger` call in\nPlaywright worker fixtures, enabling log level configuration via\nenvironment variables.\n* Modified the Playwright test runner to propagate the log level to the\ntest environment using the `SCOUT_LOG_LEVEL` variable.\n\n---------\n\nCo-authored-by: David Olaru <dolaru@vaevixen.com>","sha":"d76a5befa5ec73425b44c10b24f66a19556a7e83"}},{"branch":"9.1","label":"v9.1.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/229557","number":229557,"state":"MERGED","mergeCommit":{"sha":"1de8c338657942a87ceaa249b3a220a2ec26af92","message":"[9.1] [scout] support log level override (#228841) (#229557)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.1`:\n- [[scout] support log level override\n(#228841)](https://github.com/elastic/kibana/pull/228841)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}}]}] BACKPORT-->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto9.1:Questions ?
Please refer to the Backport tool documentation