[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-dbus
Subject:    Re: OpenTelemetry tracing of Dbus calls
From:       Umut Tezduyar Lindskog <umut () tezduyar ! com>
Date:       2023-01-11 10:09:31
Message-ID: CAFKnvs480dN5fwTQZbOEWn8kJyM+tcwcm2rjxqpZf8wqRmwwog () mail ! gmail ! com
[Download RAW message or body]

Thanks for your email Thomas.

We have around 40-50 dbus services which are the backends to http APIs. A
backend might talk to other backends. We can easily trace the HTTP APIs but
it would also be nice to add the dbus layer tracing to the overall picture.

I think it is important to understand the dbus community's interest in
OpenTelemetry. If the community is not interested then we can think about a
downstream solution. But ideally we like to contribute.

One other way that I can think of is a dedicated FD which carries the
context data. This, of course, also needs changes in the client libraries.

Umut

On Tue, Jan 10, 2023 at 12:35 PM Thomas Kluyver <thomas@kluyver.me.uk>
wrote:

> On Mon, 9 Jan 2023, at 10:28, Umut Tezduyar Lindskog wrote:
>
> Can the tracing/context data be sent over the dbus message header, granted
> this needs to be supported by the dbus client libraries?
>
>
> D-Bus has a 'header fields' array, but it doesn't allow non-standard
> headers, so to add a new field you'd need to propose a change to the spec.
> There are only 9 fields defined so far, in contrast to the dozens of
> standardised header fields for HTTP, and those 9 are all kind of integral
> to using D-Bus - there's no general metadata like the HTTP Date or Server
> headers. So I might guess this would be a tough sell, though it's not up to
> me.
>
> Have you come across specific scenarios where something you're tracing is
> using D-Bus messages and you want to follow them? Perhaps starting from a
> concrete example would make prompt more discussion than the abstract
> approach.
>
> Best wishes,
> Thomas
>

[Attachment #3 (text/html)]

<div dir="ltr">Thanks for your  email Thomas.  <div><br></div><div>We have around \
40-50 dbus services which are the backends to http APIs. A backend might talk to \
other backends. We can easily trace the HTTP APIs but it would also be nice to add \
the dbus layer tracing to the overall picture.  </div><div><br></div><div>I think it \
is important to understand the dbus community&#39;s interest in OpenTelemetry. If the \
community is not interested then we can think about a downstream  solution. But \
ideally we like to contribute.  </div><div><br></div><div>One other way that I can \
think of is a dedicated FD which carries the context data. This, of course, also \
needs changes in the client libraries.  \
</div><div><br></div><div>Umut</div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Tue, Jan 10, 2023 at 12:35 PM Thomas Kluyver &lt;<a \
href="mailto:thomas@kluyver.me.uk">thomas@kluyver.me.uk</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div \
class="msg8424147192495188868"><u></u><div><div>On Mon, 9 Jan 2023, at 10:28, Umut \
Tezduyar Lindskog wrote:<br></div><blockquote type="cite" \
id="m_8424147192495188868qt"><div dir="ltr"><div>Can the tracing/context data be sent \
over the dbus message header, granted this needs to be supported by the dbus client \
libraries?  <br></div></div></blockquote><div><br></div><div>D-Bus has a &#39;header \
fields&#39; array, but it doesn&#39;t allow non-standard headers, so to add a new \
field you&#39;d need to propose a change to the spec. There are only 9 fields defined \
so far, in contrast to the dozens of standardised header fields for HTTP, and those 9 \
are all kind of integral to using D-Bus - there&#39;s no general metadata like the \
HTTP Date or Server headers. So I might guess this would be a tough sell, though \
it&#39;s not up to me.<br></div><div><br></div><div>Have you come across specific \
scenarios where something you&#39;re tracing is using D-Bus messages and you want to \
follow them? Perhaps starting from a concrete example would make prompt more \
discussion than the abstract approach.<br></div><div><br></div><div>Best \
wishes,<br></div><div>Thomas<br></div></div></div></blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]