Before updating KQLMagic, stdout did not have INFO logging pollution. After updating to version 0.1.114.post19, stdout for the cell is "polluted" with kqlmagic logs. E.g.
* Serving Flask app 'kqlmagic_temp_files_server' (lazy loading)
* Environment: development
* Debug mode: off
2022-06-29 20:15:56,625 - INFO - start parent_monitor for parent id: 1672253
2022-06-29 20:15:56,625 - INFO - * parent id: 1672253
2022-06-29 20:15:56,625 - INFO - * Base folder: /home/<private>
2022-06-29 20:15:56,625 - INFO - * Folder list: ['.kqlmagic/temp_files/v2-1403532lpLfNUvoVYHu']
2022-06-29 20:15:56,625 - INFO - *
2022-06-29 20:15:56,625 - INFO - ****
Later on, other cells also have logging polluted stdout with messages like:
2022-06-29 20:16:57,685 - INFO - ParentProcessIdValueMonitor for ppid 1672399, parent is running.
If query related, does it happen on other platforms (Kusto Web UI, Kusto Explorer, Log Analytics in Azure Monitor)?
N/A
Output of pip freeze and %kql --bugreport
[bugreport must be executed immediatly after bug noticed]
In summary, the bug report is inconvenient to include when run from within an .ipynb notebook context. It includes a lot of user/env/connection info I don't want to share on github. In vscode notebooks, its output exceeds cell size limit, and the default colored syntax highlighting makes the raw view of output "corrupted" with terminal colour escape codes. So the broken JSON is due to '...' when vscode noteboook display limits cell output length. I attempted a partial extract with the logs cut short as they starting spilling subscription/env info all over the place and I decided to omit all connection specific sections/identifiers. The kqlmagic_default_options section has the ... due to cell length limitations.
Code Sample, a copy-pastable example if possible
E.g. in a given cell
Problem description
Before updating KQLMagic, stdout did not have INFO logging pollution. After updating to version 0.1.114.post19, stdout for the cell is "polluted" with kqlmagic logs. E.g.
Later on, other cells also have logging polluted stdout with messages like:
If query related, does it happen on other platforms (Kusto Web UI, Kusto Explorer, Log Analytics in Azure Monitor)?
N/A
Output of
pip freeze
and%kql --bugreport
[bugreport must be executed immediatly after bug noticed]
Kqlmagic bug report #4ebb5139-7d46-4d7f-b7af-aa61be804fdd
In summary, the bug report is inconvenient to include when run from within an .ipynb notebook context. It includes a lot of user/env/connection info I don't want to share on github. In vscode notebooks, its output exceeds cell size limit, and the default colored syntax highlighting makes the raw view of output "corrupted" with terminal colour escape codes. So the broken JSON is due to '...' when vscode noteboook display limits cell output length. I attempted a partial extract with the logs cut short as they starting spilling subscription/env info all over the place and I decided to omit all connection specific sections/identifiers. The kqlmagic_default_options section has the
...
due to cell length limitations.[paste the output of
pip freeze
here below this line]