Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate log channel for device status #1280

Open
bobrippling opened this issue May 30, 2024 · 0 comments
Open

Separate log channel for device status #1280

bobrippling opened this issue May 30, 2024 · 0 comments

Comments

@bobrippling
Copy link

Description

I'm happy to do the work, but want to confirm this approach is ok and would be accepted.

I notice a lot of bus errors appear (such as the SYN error below) and I would like to avoid them in my logs (using --log=bus:none):

[bus error] poll bai PrEnergySumHwc3 failed: ERR: SYN received

Unfortunately this solution (--log=bus:none) also silences two errors which I'd like to keep, namely:

[bus error] device status: eBUS comm error: overrun
[bus error] device status: transport closed

I would propose to move these two errors to a log facility, lf_device, to allow users to retain these errors, while ignoring regular SYN errors. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant