PCP: support for 'dynamic columns' added at runtime
Implements support for arbitrary Performance Co-Pilot
metrics with per-process instance domains to form new
htop columns. The column-to-metric mappings are setup
using configuration files which will be documented via
man pages as part of a follow-up commit.
We provide an initial set of column configurations so
as to provide new capabilities to pcp-htop: including
configs for containers, open fd counts, scheduler run
queue time, tcp/udp bytes/calls sent/recv, delay acct,
virtual machine guests, detailed virtual memory, swap.
Note there is a change to the configuration file path
resolution algorithm introduced for 'dynamic meters'.
First, look in any custom PCP_HTOP_DIR location. Then
iterate, in priority order, users home directory, then
local sysadmins files in /etc/pcp/htop, then readonly
configuration files below /usr/share/pcp/htop. This
final location becomes the preferred place for our own
shipped meter and column files.
The Settings file (htoprc) writing code is updated to
not using the numeric identifier for dynamic columns.
The same strategy used for dynamic meters is used here
where we write Dynamic(name) so the name can be setup
once more at start. Regular (static) columns writing
to htoprc - i.e. numerically indexed - is unchanged.
2021-07-11 01:11:29 +00:00
|
|
|
#ifndef HEADER_PCPDynamicColumn
|
|
|
|
#define HEADER_PCPDynamicColumn
|
|
|
|
|
2021-08-14 21:30:19 +00:00
|
|
|
#include <stddef.h>
|
|
|
|
|
PCP: support for 'dynamic columns' added at runtime
Implements support for arbitrary Performance Co-Pilot
metrics with per-process instance domains to form new
htop columns. The column-to-metric mappings are setup
using configuration files which will be documented via
man pages as part of a follow-up commit.
We provide an initial set of column configurations so
as to provide new capabilities to pcp-htop: including
configs for containers, open fd counts, scheduler run
queue time, tcp/udp bytes/calls sent/recv, delay acct,
virtual machine guests, detailed virtual memory, swap.
Note there is a change to the configuration file path
resolution algorithm introduced for 'dynamic meters'.
First, look in any custom PCP_HTOP_DIR location. Then
iterate, in priority order, users home directory, then
local sysadmins files in /etc/pcp/htop, then readonly
configuration files below /usr/share/pcp/htop. This
final location becomes the preferred place for our own
shipped meter and column files.
The Settings file (htoprc) writing code is updated to
not using the numeric identifier for dynamic columns.
The same strategy used for dynamic meters is used here
where we write Dynamic(name) so the name can be setup
once more at start. Regular (static) columns writing
to htoprc - i.e. numerically indexed - is unchanged.
2021-07-11 01:11:29 +00:00
|
|
|
#include "DynamicColumn.h"
|
|
|
|
#include "Hashtable.h"
|
|
|
|
#include "Process.h"
|
|
|
|
#include "RichString.h"
|
|
|
|
|
|
|
|
#include "pcp/PCPProcess.h"
|
|
|
|
|
|
|
|
|
|
|
|
typedef struct PCPDynamicColumn_ {
|
|
|
|
DynamicColumn super;
|
|
|
|
char* metricName;
|
|
|
|
size_t id; /* identifier for metric array lookups */
|
|
|
|
} PCPDynamicColumn;
|
|
|
|
|
|
|
|
typedef struct PCPDynamicColumns_ {
|
|
|
|
Hashtable* table;
|
|
|
|
size_t count; /* count of dynamic meters discovered by scan */
|
|
|
|
size_t offset; /* start offset into the Platform metric array */
|
|
|
|
size_t cursor; /* identifier allocator for each new metric used */
|
|
|
|
} PCPDynamicColumns;
|
|
|
|
|
|
|
|
void PCPDynamicColumns_init(PCPDynamicColumns* columns);
|
|
|
|
|
|
|
|
void PCPDynamicColumn_writeField(PCPDynamicColumn* this, const Process* proc, RichString* str);
|
|
|
|
|
|
|
|
int PCPDynamicColumn_compareByKey(const PCPProcess* p1, const PCPProcess* p2, ProcessField key);
|
|
|
|
|
|
|
|
#endif
|