This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/18848] New: new --monitor option
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 18 Aug 2015 08:14:18 +0000
- Subject: [Bug runtime/18848] New: new --monitor option
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18848
Bug ID: 18848
Summary: new --monitor option
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
As a part of the interactive-systemtap effort, we'd like to have a way of
compiling stap modules so that they can report on their own status, and give a
way to control them from the outside.
For example, a new option "stap --monitor" could emit extra code into the
module, so that:
- it presents a procfs interface by which stats like this are available:
- module name, invoker uid, sizes (as per startup dmesg)
- number of warnings, errors; maybe text of recent errors
- list of global variables (incl. array sizes)
- abbreviated list of probes (incl. hit count/times as per stap -t)
- it presents another procfs interface by which control may be exercised:
- to disable or enable probes (as if by hidden on-the-fly control variables)
- to reset the global variables (so as to start the script anew)
- to exit the script
Then the stapio program can connect to those two proc interfaces, poll the
former to display, map keyboard inputs for sending to the other. (The stap
--interactive front-end can later also do the same.)
--
You are receiving this mail because:
You are the assignee for the bug.