all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH manager] report: list recent reboot events and their kernel version
Date: Wed, 05 Aug 2026 10:21:29 +0200	[thread overview]
Message-ID: <s8o4ih9ou46.fsf@toolbox> (raw)
In-Reply-To: <e503269b-bd3d-4122-bf98-8ead07de05b9@proxmox.com> (Thomas Lamprecht's message of "Mon, 20 Jul 2026 17:41:00 +0200")

Thomas Lamprecht <t.lamprecht@proxmox.com> writes:

> Am 20.07.26 um 16:58 schrieb Alexander Zeidler:
> [..]
> FWIW, we already got proxmox-mini-journalreader and it can already produce
> json that we could extend to produce the relevant info, i.e. iterating through
> boots (IIRC that is a indexed table) and parser first Line to extract the
> kernel. That could then be outputted as structured JSON there which can be
> parsed by the report here. In the midterm we could even think about integrating
> that as fully fledged API to our products API, if it can provide value as first
> class boot + kernel list there. For now just parsing the json in the report
> would be more than enough (or CLI only integration as middleground).
>
> You can try "poaching" one of our Devs that isn't to afraid from a bit of
> C to implement this, would be probably the safest course be here, especially
> as we maintain the journald handling already anyway.

I tried my hand at this, see
https://lore.proxmox.com/all/20260805081911.131557-1-m.sandoval@proxmox.com/T/#u.

The json output part is not implemented, but for our interests this is
perfectly OK.

-- 
Maximiliano




  reply	other threads:[~2026-08-05  8:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 12:33 [PATCH manager] report: list recent reboot events and their kernel version Alexander Zeidler
2026-07-20 12:58 ` Thomas Lamprecht
2026-07-20 13:33   ` Maximiliano Sandoval
2026-07-20 14:58     ` Alexander Zeidler
2026-07-20 15:41       ` Thomas Lamprecht
2026-08-05  8:21         ` Maximiliano Sandoval [this message]
2026-07-20 13:16 ` Maximiliano Sandoval

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=s8o4ih9ou46.fsf@toolbox \
    --to=m.sandoval@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal