search

bbindreiter / node-red-contrib-alexa-remote2-applestrudel

Node-Red Nodes for interacting with Alexa
https://flows.nodered.org/node/node-red-contrib-alexa-remote2-applestrudel
MIT License
78 stars 21 forks source link

debug logging too verbose #187

Closed tethlah closed 6 months ago

tethlah commented 7 months ago

It seems like enabling debug logging is outputting what I should be seeing at trace level. I'm trying to troubleshoot an issue with something else, but the debug output is being flooded by the responses from alexa. There's no deference between debug and trace with the alexa output. The fully verbose outputs should be in trace and not debug.

tethlah commented 7 months ago

So the issue I've been trying to track down is that my node red instance keeps randomly restarting a few times per day over the last couple weeks. Since the log was flooded by the Alexa node, I decided to disable it to clear up my debug log so I could troubleshoot what's happening just before restart. It hasn't restarted since I disabled the Alexa Config node. So it looks like something with this node is what's causing my constant reboots. It's pretty hard debug what's going on though because the logs are flooded with the Alexa responses from the requests in the node.

github-actions[bot] commented 6 months ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 6 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.

tethlah commented 5 months ago

Any chance anything has been done with how verbose the debug log is since I originally brought it up? I'd like to go back to using this but the debug logs are unusable when they are at a trace level.