File: 352.out

package info (click to toggle)
pcp 7.1.0-1
  • links: PTS
  • area: main
  • in suites: forky, sid
  • size: 252,748 kB
  • sloc: ansic: 1,483,656; sh: 182,366; xml: 160,462; cpp: 83,813; python: 24,980; perl: 18,327; yacc: 6,877; lex: 2,864; makefile: 2,738; awk: 165; fortran: 60; java: 52
file content (153 lines) | stat: -rw-r--r-- 4,518 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
QA output created by 352
Expect this to fail as derived metrics not defined ...
Log for pmlogger on HOST started DATE

[DATE] pmlogger(PID) Info: Start
Warning [TMP.config, line 5]
Problem with lookup for metric "sample.long.nine" ... logging not activated
Reason: Unknown metric name
Warning [TMP.config, line 6]
Problem with lookup for metric "sample.long.ninety_nine" ... logging not activated
Reason: Unknown metric name
Warning [TMP.config, line 7]
Problem with lookup for metric "sample.long.lots" ... logging not activated
Reason: Unknown metric name
Config parsed
Starting logger for host "HOST"
Archive basename: ARCHIVE
[DATE] pmlogger(PID) Info: pmlogger: Sample limit reached, exiting

Log finished DATE

Metric Help Text in the Log ...
PMID: 29.0.10 [1 as a 32-bit integer]
PMID: 29.0.10
The sample.long.* metrics provide a group of 32-bit integer metrics
some with fixed values and one with a value that can be changed via
pmstore(1).

This one has the constant value 1.
PMID: 29.0.11 [10 as a 32-bit integer]
PMID: 29.0.11


TIMESTAMP 5 metrics

TIMESTAMP 2 metrics
    29.0.11 (sample.long.ten): value 10
    29.0.10 (sample.long.one): value 1

TIMESTAMP 2 metrics
    29.0.11 (sample.long.ten): value 10
    29.0.10 (sample.long.one): value 1

TIMESTAMP 5 metrics

Now with derived metrics defined ...

sample.long.one
    value 1

sample.long.ten
    value 10

sample.long.nine
    value 9

sample.long.ninety_nine
    value 99

sample.long.lots
    value 999900
Log for pmlogger on HOST started DATE

[DATE] pmlogger(PID) Info: Start
Config parsed
Starting logger for host "HOST"
Archive basename: ARCHIVE
[DATE] pmlogger(PID) Info: pmlogger: Sample limit reached, exiting

Log finished DATE

Metric Help Text in the Log ...
PMID: 29.0.10 [1 as a 32-bit integer]
PMID: 29.0.10
The sample.long.* metrics provide a group of 32-bit integer metrics
some with fixed values and one with a value that can be changed via
pmstore(1).

This one has the constant value 1.
PMID: 29.0.11 [10 as a 32-bit integer]
PMID: 29.0.11

PMID: 511.2048.3 [This should be 9!]
PMID: 511.2048.4
Since this is 100 minus 1, we'd expect the answer to be exactly
>>> 99 <<<
on most days
PMID: 511.2048.5 [This should be 999900!]
PMID: 511.2048.5
Since this is 1,0000 minus 100 the answer is expected to be very
close to 999900, n'est ce pas?

TIMESTAMP 5 metrics

TIMESTAMP 5 metrics
    511.2048.5 (sample.long.lots): value 999900
    511.2048.4 (sample.long.ninety_nine): value 99
    511.2048.3 (sample.long.nine): value 9
    29.0.11 (sample.long.ten): value 10
    29.0.10 (sample.long.one): value 1

TIMESTAMP 5 metrics
    511.2048.5 (sample.long.lots): value 999900
    511.2048.4 (sample.long.ninety_nine): value 99
    511.2048.3 (sample.long.nine): value 9
    29.0.11 (sample.long.ten): value 10
    29.0.10 (sample.long.one): value 1

TIMESTAMP 5 metrics
    511.2048.5 (sample.long.lots): value 999900
    511.2048.4 (sample.long.ninety_nine): value 99
    511.2048.3 (sample.long.nine): value 9
    29.0.11 (sample.long.ten): value 10
    29.0.10 (sample.long.one): value 1

TIMESTAMP 5 metrics

sample.long.one [1 as a 32-bit integer]
    labels {"agent":"sample","domainname":"DOMAINNAME","groupid":GROUPID,"hostname":"HOSTNAME","machineid":"MACHINEID","role":"testing","userid":USERID}
Help:
The sample.long.* metrics provide a group of 32-bit integer metrics
some with fixed values and one with a value that can be changed via
pmstore(1).

This one has the constant value 1.
    value 1

sample.long.ten [10 as a 32-bit integer]
    labels {"agent":"sample","domainname":"DOMAINNAME","groupid":GROUPID,"hostname":"HOSTNAME","machineid":"MACHINEID","role":"testing","userid":USERID}
Help:
10 as a 32-bit integer
    value 10

sample.long.nine [This should be 9!]
    labels {"domainname":"DOMAINNAME","groupid":GROUPID,"hostname":"HOSTNAME","machineid":"MACHINEID","userid":USERID}
Help:
This should be 9!
    value 9

sample.long.ninety_nine One-line Help: Error: One-line or help text is not available
    labels {"domainname":"DOMAINNAME","groupid":GROUPID,"hostname":"HOSTNAME","machineid":"MACHINEID","userid":USERID}
Help:
Since this is 100 minus 1, we'd expect the answer to be exactly
>>> 99 <<<
on most days
    value 99

sample.long.lots [This should be 999900!]
    labels {"domainname":"DOMAINNAME","groupid":GROUPID,"hostname":"HOSTNAME","machineid":"MACHINEID","userid":USERID}
Help:
Since this is 1,0000 minus 100 the answer is expected to be very
close to 999900, n'est ce pas?
    value 999900