Document device.listen_addr and Handling Twisted Web Logs

[nbuuckssi]

Proposed changes

This PR documents what I learned about Twisted HTTP logs that continued to appear in my host's syslog despite removing the default Syslog and Console handler's from my OpenCanary installation's configuration. This duplication of HTTP logs was undesirable because another security tool was capturing both the syslog and the JSON logged by my OpenCanary configuration to a rotating file in /var/log.

This PR also documents the seemingly-undocumented device.listen_addr configuration option added in #337.

Types of changes

What types of changes does your code introduce to this repository? Put an x in the boxes that apply

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [X] Documentation Update

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [ ] Lint and unit tests pass locally with my changes (if applicable)
• [ ] I have run pre-commit (pre-commit in the repo)
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (if appropriate)
• [ ] Linked to the relevant github issue or github discussion

[nbuuckssi]

I suppose it's worth considering whether device.listen_addr should just be added to the default configuration file in lieu of adding the table presently in this PR. The table has the advantage of being able to explain the caveat that it only applies to certain modules.