You can filter of course. And if the entries are expanded, you can use your browser's Find on Page to search. You also need to remember that the outputs are restricted by default to 1k of text.
If you need more, a custom logger might be useful to you. You would output the debug data to log and use a custom logger function in settings.js - you could then output the data in a way that lets you have a separate browser tab. I do that so that I can have uibuilder trace logging without having to wade through trace logs for everything.
In settings.js logging property:
mqttLog: {
level: 'trace',
metrics: false,
audit: false,
handler: function (settings) {
const nrLogLevels = {
10: 'FATAL', 20: 'ERROR', 30: 'WARN ', 40: 'INFO ', 50: 'DEBUG', 60: 'TRACE', 98: 'AUDIT', 99: 'MTRIC'
}
const myCustomLevels = {
levels: {
'FATAL': 10,
'ERROR': 20,
'WARN ': 30,
'INFO ': 40,
'DEBUG': 50,
'TRACE': 60,
'AUDIT': 98,
'MTRIC': 99
},
colors: {
'FATAL': 'redBG',
'ERROR': 'red',
'WARN ': 'orange',
'INFO ': 'yellow',
'DEBUG': 'green',
'TRACE': 'cyan',
'AUDIT': 'grey',
'MTRIC': 'grey'
}
}
const mqtt = require('mqtt')
const client = mqtt.connect('mqtt://home.knightnet.co.uk')
return function (msg) {
if (msg.level < 51 || msg.msg.includes('[uibuilder') || msg.msg.startsWith('+-') || msg.msg.startsWith('| ') || msg.msg.startsWith('>>')) {
client.publish('nrlog/live', JSON.stringify(msg))
}
}
}
},
So the log output that I'm interested is sent a message at a time to an MQTT topic. I then use a simple flow (just a single uibuilder node) to provide an output web endpoint. In my case, I add an MQTT library direct to the page to listen to the MQTT output but of course you could also manage that via Node-RED instead.
