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

Unify logging to make it possible to easily and cleanly log to different destinations #1558

Closed
woju opened this Issue Dec 29, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@woju
Member

woju commented Dec 29, 2015

Logging from qvm-tools ends up in four places:

  • stderr (controlled by -q/-v)
  • file (/var/log/qubes or something)
  • possibly syslog
  • freedesktop notification on dbus (formerly controlled by --tray, what now?)

There should be an agreement on:

  • which messages go where (this gets complicated when there are many possible levels with -q/-v)
  • how to assign a level to a particular message
  • which messages should go over dbus (what's their threshold)
  • what syslog facility we log to and mapping between syslog levels and python's numerical levels

/cc @marmarek, low priority

@woju woju added the C: core label Dec 29, 2015

@woju woju self-assigned this Dec 29, 2015

@woju woju added this to the Release 4.0 milestone Dec 29, 2015

@woju

This comment has been minimized.

Show comment
Hide comment
@woju

woju Dec 29, 2015

Member

corner case: qubes.tests.run

Member

woju commented Dec 29, 2015

corner case: qubes.tests.run

@woju

This comment has been minimized.

Show comment
Hide comment
@woju

woju Apr 18, 2018

Member

This issue is abandoned, so I'm going to close it. If that's a mistake, feel free to reopen.
@marmarek @andrewdavidwong

Member

woju commented Apr 18, 2018

This issue is abandoned, so I'm going to close it. If that's a mistake, feel free to reopen.
@marmarek @andrewdavidwong

@woju woju closed this Apr 18, 2018

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