Skip to content

Commit

Permalink
Applied suggested changes
Browse files Browse the repository at this point in the history 
Signed-off-by: Elena Khaustova <ymax70rus@gmail.com>
  • Loading branch information
@ElenaKhaustova
ElenaKhaustova committed Jun 27, 2024
1 parent b703d39 commit cc1b8ea
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/source/logging/index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -44,8 +44,8 @@ If the `KEDRO_LOGGING_CONFIG` environment variable is not set, Kedro will use th

### Change the verbosity of specific parts of Kedro

You can also customise logging at the runtime and redefine the logging configuration provided in the `logging.yml` when using jupyter notebook.
In the example below we change a logging level to `WARNING` for the `kedro.io.data_catalog` component logger specifically, the logging for the rest of the components will remain unchanged.
You can also customise logging at runtime and redefine the logging configuration provided in the `logging.yml` when using jupyter notebook.

Check warning on line 47 in docs/source/logging/index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/source/logging/index.md#L47 

[Kedro.Spellings] Did you really mean 'jupyter'?
Raw output 
{"message": "[Kedro.Spellings] Did you really mean 'jupyter'?", "location": {"path": "docs/source/logging/index.md", "range": {"start": {"line": 47, "column": 123}}}, "severity": "WARNING"}
The example below demonstrates how you can change the logging level from default `INFO` to `WARNING` for the `kedro.io.data_catalog` component logger specifically, the logging for the rest of the components will remain unchanged.
The same can be done for higher/lower-level components without affecting the top-level.

Add the following to a cell in your notebook:
Expand Down

0 comments on commit cc1b8ea

Please sign in to comment.