[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230705082604.7b104a48@hermes.local>
Date: Wed, 5 Jul 2023 08:26:04 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Breno Leitao <leitao@...ian.org>
Cc: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, sergey.senozhatsky@...il.com,
pmladek@...e.com, tj@...nel.org,
Dave Jones <davej@...emonkey.org.uk>,
"open list:NETWORKING DRIVERS" <netdev@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] netconsole: Append kernel version to message
On Wed, 5 Jul 2023 02:18:03 -0700
Breno Leitao <leitao@...ian.org> wrote:
> The uname is useful if the receiver side is looking (grepping) for
> specific messages (warnings, oops, etc) affecting specific kernel
> versions. If the uname is not available, the receiver needs to read boot
> message and keep a map for source IP to kernel version. This is far from
> ideal at a hyperscale level.
At hyperscale you need a real collector (not just netcat) that can consult
the VM database to based on IP and record the meta data there. If you allow
random updates and versions, things get out of control real fast and this
won't really help much
Powered by blists - more mailing lists