[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251024135301.0ed4b57d@gandalf.local.home>
Date: Fri, 24 Oct 2025 13:53:01 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Alex Markuze <amarkuze@...hat.com>
Cc: ceph-devel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Liam.Howlett@...cle.com, akpm@...ux-foundation.org,
bsegall@...gle.com, david@...hat.com, dietmar.eggemann@....com,
idryomov@...il.com, mingo@...hat.com, juri.lelli@...hat.com,
kees@...nel.org, lorenzo.stoakes@...cle.com, mgorman@...e.de,
mhocko@...e.com, rppt@...nel.org, peterz@...radead.org, surenb@...gle.com,
vschneid@...hat.com, vincent.guittot@...aro.org, vbabka@...e.cz,
xiubli@...hat.com, Slava.Dubeyko@....com
Subject: Re: [RFC PATCH 0/5] BLOG: per-task logging contexts with Ceph
consumer
On Fri, 24 Oct 2025 08:42:54 +0000
Alex Markuze <amarkuze@...hat.com> wrote:
> Motivation: improve observability in production by providing subsystemsawith
> a logger that keeps up with their verbouse unstructured logs and aggregating
> logs at the process context level, akin to userspace TLS.
>
I still don't understand the motivation behind this.
What exactly is this doing that the current tracing infrastructure can't do?
-- Steve
Powered by blists - more mailing lists