All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Deprecate phosphor-hostlogger?
Date: Wed, 9 Jul 2025 09:53:35 -0400	[thread overview]
Message-ID: <aG50XyECFuxmDkXB@heinlein> (raw)

[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]

Hello,

Does anyone have opinions on if we deprecate phosphor-hostlogger?

I ended up becoming the "maintainer" of it due to the original maintainers
no longer being able to contribute to OpenBMC.  I've read through the
README and it is very much not clear to me what advantages it has over
using the similar functionality contained in obmc-console directly.
There is some mention of rsyslog and logrotate integration, but
obmc-console already supports a logrotate-like functionality, and I
think rsyslog could be easily configured to pick up the log files
created by obmc-console, if someone were so inclined.

It appears to only be used by the following meta layers:

    * meta-amd
    * meta-ampere
    * meta-bytedance
    * meta-quanta / s6q
    * meta-tyan
    * meta-yadro

It seems that this repository also incurred some bmcweb support that is
enabled for most systems (by default), even though they do not have the
corresponding daemon.

Can any of the system owners above comment as to what functionality they
are gaining by using phosphor-hostlogger over using obmc-console
directly?  Is this some functionality missing from obmc-console or is it
just a relationship between host logging, bmcweb and rsyslog that we
need to add?

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2025-07-09 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 13:53 Patrick Williams [this message]
2025-07-09 19:45 ` Deprecate phosphor-hostlogger? Ed Tanous

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aG50XyECFuxmDkXB@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.