[
https://issues.apache.org/jira/browse/UNOMI-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Griffon updated UNOMI-844:
--------------------------------
Description:
The tracker is generating too much js logs in the console.
As the logs still relevant for development or debug, we have to move them from
{code}
console.log()
{code}
to
{code}
console.debug()
{code}
To enable debug log level on Chrome, you have to set the log level to *verbose*
!enable debug log level on chrome.png!
was:
The tracker is generating too much js logs in the console.
As the logs still relevant for development or debug, we have to move them from
{code}
console.log()
{code}
to
{code}
console.debug()
{code}
To enable debug log level on Chrome, you have to set the log level to *verbose*
> move console logs to debugs
> ---------------------------
>
> Key: UNOMI-844
> URL: https://issues.apache.org/jira/browse/UNOMI-844
> Project: Apache Unomi
> Issue Type: Task
> Components: unomi-tracker
> Affects Versions: unomi-tracker-1.4.0
> Reporter: David Griffon
> Priority: Major
> Attachments: enable debug log level on chrome.png
>
>
> The tracker is generating too much js logs in the console.
> As the logs still relevant for development or debug, we have to move them from
> {code}
> console.log()
> {code}
> to
> {code}
> console.debug()
> {code}
> To enable debug log level on Chrome, you have to set the log level to
> *verbose*
> !enable debug log level on chrome.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
