All of lore.kernel.org
 help / color / mirror / Atom feed
From: Victor Kamensky <kamensky@cisco.com>
To: Martin Jansa <martin.jansa@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] systemtap: 3.3 -> 4.0
Date: Thu, 25 Oct 2018 20:37:50 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.00.1810252000220.5649@sjc-ads-6991.cisco.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1810171314560.37492@sjc-ads-6991.cisco.com>

Hi Guys,

On Wed, 17 Oct 2018, Victor Kamensky wrote:

> stap-exporter service is a new feature in SystemTap 4.0, I've never used
> it before. I'll dig in and will try to make sure that it is functional
> in resulting OE image.

I've had a chance to look at stap-exporter and its service more closely.

It looks like it is simple HTTP server that allows to run stap scripts
on target and relay its information to Prometheus monitoring system.
Please check.

https://www.mankier.com/8/stap-exporter

https://prometheus.io

Since it is HTTP server, and its man page says that it is not supposed
to run in untrusted environment I am quite hesitant to have it enabled
by default. Moreover, it comes with some default example scripts that
actually fail to compile in OE core-image-lsb-sdk because it does not
include kernel-vmlinux package by default. stap-exporter is not
prepared to handle script compilation failure and tries to compile it
in the loop, so in core-image-lsb-sdk systemd image where 
stap-exporter.service would be enabled by default it would trash the
system.

Considering all that I suggest stap-exporter to be moved in separate
systemtap-exporter package, so it can be installed explcitely. I
posted patch for it at

http://lists.openembedded.org/pipermail/openembedded-core/2018-October/157073.html

BTW in FC it is separate systemtap-exporter package.

I've tested systemtap-exporter and stap-exporter, if installed
along with proper prerequisites (kernel-vmlinux) is functioning
OK with given default example as far as my manual http testing
with curl shows. I did not test it with prometheus.

Thanks,
Victor


      reply	other threads:[~2018-10-26  3:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 18:21 [PATCH] systemtap: 3.3 -> 4.0 Victor Kamensky
2018-10-15 21:02 ` Randy MacLeod
2018-10-16  3:54   ` Victor Kamensky
2018-10-16  9:27 ` Burton, Ross
2018-10-16  9:54   ` Richard Purdie
2018-10-17  5:56     ` Victor Kamensky
2018-10-17 11:59       ` richard.purdie
2018-10-17 14:50         ` Martin Jansa
2018-10-17 15:07           ` richard.purdie
2018-10-17 19:01             ` Martin Jansa
2018-10-17 19:03               ` [PATCH] systemtap: fix QA issue Martin Jansa
2018-10-17 20:21               ` [PATCH] systemtap: 3.3 -> 4.0 Victor Kamensky
2018-10-26  3:37                 ` Victor Kamensky [this message]

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=alpine.LRH.2.00.1810252000220.5649@sjc-ads-6991.cisco.com \
    --to=kamensky@cisco.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.