You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Domain** - the first single-word prefix that represents a metric type. The examples of domain-level prefixes are: system, mq, mqobject and etc. More information can be found in ["Domains and subdomains" section](#domains-and-subdomains).
189
+
-**Subdomain** - second single-word prefix representation of a metric type. It provides more specific information about metric type and helps to differentiate metrics in a single domain. The examples of subdomain-level prefixes are: cpu, ram, put, subscribe, get and etc. More information can be found in ["Domains and subdomains" section](#domains-and-subdomains).
190
+
-**Units** - single-word suffix describing the metric's unit, in plural form. Note that an accumulating count has "total" as the first part of a suffix. The examples of unit suffixes are: percentage, hundredths, messages, totalmessages and etc. More information can be found in ["Units" section](#units).
191
+
-**Name** - represents metric meaning. The examples of a metric name are: cpu_time, cpu_load_fifteen_minute_average, failed_mqget_count and etc. Note that the amount of words in a metric name can vary:
<td>Disk usage metrics, related to a running queue manager</td>
224
+
</tr>
225
+
<tr>
226
+
<td>rlog</td>
227
+
<td>Queue manager recovery log metrics</td>
228
+
</tr>
229
+
<tr>
230
+
<td>mqconn</td>
231
+
<td>Metrics related to MQCONN calls to a queue manager</td>
232
+
</tr>
233
+
<tr>
234
+
<td>mqdisc</td>
235
+
<td>Metrics related to MQDISC calls to a queue manager</td>
236
+
</tr>
237
+
<tr>
238
+
<td>mqopen</td>
239
+
<td>Metrics related to MQOPEN calls to a queue manager</td>
240
+
</tr>
241
+
<tr>
242
+
<td>mqclose</td>
243
+
<td>Metrics related to MQCLOSE calls to a queue manager</td>
244
+
</tr>
245
+
<tr>
246
+
<td>mqinq</td>
247
+
<td>Metrics related to MQINQ calls to a queue manager</td>
248
+
</tr>
249
+
<tr>
250
+
<td>mqset</td>
251
+
<td>Metrics related to MQSET calls to a queue manager</td>
252
+
</tr>
253
+
<tr>
254
+
<td>put</td>
255
+
<td>Metrics related to MQPUT, MQPUT1 and MQSTAT calls to a queue manager</td>
256
+
</tr>
257
+
<tr>
258
+
<td>get</td>
259
+
<td>Metrics related to MQGET, MQCB and MQCTL calls to a queue manager</td>
260
+
</tr>
261
+
<tr>
262
+
<td>commit</td>
263
+
<td>Metrics related to MQCMIT calls to a queue manager</td>
264
+
</tr>
265
+
<tr>
266
+
<td>rollback</td>
267
+
<td>Metrics related to MQBACK calls to a queue manager</td>
268
+
</tr>
269
+
<tr>
270
+
<td>subscribe</td>
271
+
<td>Metrics related to subscriptions of a queue manager</td>
272
+
</tr>
273
+
<tr>
274
+
<td>publish</td>
275
+
<td>Metrics related to publications of a queue manager</td>
276
+
</tr>
277
+
<tr>
278
+
<tdrowspan="9">mqobject</td>
279
+
<tdrowspan="9">Metrics for specific objects of a queue manager: for a queue, for a channel, for a listener</td>
280
+
<td>mqopen</td>
281
+
<td>Metrics related to MQOPEN calls to a specific queue</td>
282
+
</tr>
283
+
<tr>
284
+
<td>mqclose</td>
285
+
<td>Metrics related to MQCLOSE calls to a specific queue</td>
286
+
</tr>
287
+
<tr>
288
+
<td>mqinq</td>
289
+
<td>Metrics related to MQINQ calls to a specific queue</td>
290
+
</tr>
291
+
<tr>
292
+
<td>mqset</td>
293
+
<td>Metrics related to MQSET calls to a specific queue</td>
294
+
</tr>
295
+
<tr>
296
+
<td>put</td>
297
+
<td>Metrics related to MQPUT and MQPUT1 calls to a specific queue</td>
298
+
</tr>
299
+
<tr>
300
+
<td>get</td>
301
+
<td>Metrics related to MQGET calls to a specific queue</td>
302
+
</tr>
303
+
<tr>
304
+
<td>queue</td>
305
+
<td>Metrics related to a specific queue</td>
306
+
</tr>
307
+
<tr>
308
+
<td>channel</td>
309
+
<td>Metrics related to a specific channel</td>
310
+
</tr>
311
+
<tr>
312
+
<td>listener</td>
313
+
<td>Metrics related to a specific listener</td>
314
+
</tr>
315
+
</tbody>
316
+
</table>
317
+
318
+
###### Units
319
+
320
+
["Metric and label naming"](https://prometheus.io/docs/practices/naming/#metric-and-label-naming) article by Prometheus states that metrics "...should use base units (e.g. seconds, bytes, meters - not milliseconds, megabytes, kilometers)". But it is not usefull for using IBM MQ exporter. So the exporter has following list of units:
321
+
322
+
<table>
323
+
<tbody>
324
+
<tr>
325
+
<td><strong>Unit</strong></td>
326
+
<td><strong>Unit description</strong></td>
327
+
</tr>
328
+
<tr>
329
+
<td>percentage</td>
330
+
<td>Shows %</td>
331
+
</tr>
332
+
<tr>
333
+
<td>hundredths</td>
334
+
<td>Shows amount of hundredths. For example, "370 hundredths equal" to "3.70". It is used to reflect system's load average.</td>
335
+
</tr>
336
+
<tr>
337
+
<td>megabytes</td>
338
+
<td>Shows amount of megabytes</td>
339
+
</tr>
340
+
<tr>
341
+
<td>files</td>
342
+
<td>Shows amount of files</td>
343
+
</tr>
344
+
<tr>
345
+
<td>bytes</td>
346
+
<td>Shows amount of bytes</td>
347
+
</tr>
348
+
<tr>
349
+
<td>microseconds</td>
350
+
<td>Shows amount of microseconds.</td>
351
+
</tr>
352
+
<tr>
353
+
<td>totalcalls</td>
354
+
<td>Shows amount of calls. An accumulating count has "total" as the first part of a suffix.</td>
355
+
</tr>
356
+
<tr>
357
+
<td>totalconnections</td>
358
+
<td>Shows amount of connections. An accumulating count has "total" as the first part of a suffix.</td>
359
+
</tr>
360
+
<tr>
361
+
<td>totalmessages</td>
362
+
<td>Shows amount of messages. An accumulating count has "total" as the first part of a suffix.</td>
363
+
</tr>
364
+
<tr>
365
+
<td>totalbytes</td>
366
+
<td>Shows amount of bytes. An accumulating count has "total" as the first part of a suffix.</td>
367
+
</tr>
368
+
<tr>
369
+
<td>totalbrowses</td>
370
+
<td>Shows amount of browses. An accumulating count has "total" as the first part of a suffix.</td>
371
+
</tr>
372
+
<tr>
373
+
<td>subscriptions</td>
374
+
<td>Shows amount of subscriptions.</td>
375
+
</tr>
376
+
<tr>
377
+
<td>totalattempts</td>
378
+
<td>Shows amount of attempts. An accumulating count has "total" as the first part of a suffix.</td>
379
+
</tr>
380
+
<tr>
381
+
<td>totalqueues</td>
382
+
<td>Shows amount of queues. An accumulating count has "total" as the first part of a suffix.</td>
383
+
</tr>
384
+
<tr>
385
+
<td>messages</td>
386
+
<td>Shows amount of messages.</td>
387
+
</tr>
388
+
</tbody>
389
+
</table>
390
+
391
+
#### Metrics list
392
+
##### Platform central processing units
178
393
###### CPU performance - platform wide
179
394
<table>
180
395
<tbody>
@@ -259,7 +474,7 @@ The only input parameter is the path to your configuration file.
259
474
</tbody>
260
475
</table>
261
476
262
-
#### Platform persistent data stores
477
+
#####Platform persistent data stores
263
478
###### Disk usage - platform wide
264
479
<table>
265
480
<tbody>
@@ -380,7 +595,7 @@ The only input parameter is the path to your configuration file.
380
595
</tbody>
381
596
</table>
382
597
383
-
#### API usage statistics
598
+
#####API usage statistics
384
599
###### MQCONN and MQDISC
385
600
<table>
386
601
<tbody>
@@ -858,7 +1073,7 @@ The only input parameter is the path to your configuration file.
858
1073
</tbody>
859
1074
</table>
860
1075
861
-
#### API per-queue usage statistics
1076
+
#####API per-queue usage statistics
862
1077
###### MQOPEN and MQCLOSE
863
1078
<table>
864
1079
<tbody>
@@ -1080,8 +1295,8 @@ The only input parameter is the path to your configuration file.
1080
1295
</tbody>
1081
1296
</table>
1082
1297
1083
-
#### MQ PCF API specific statistics
1084
-
##### PCF requests
1298
+
#####MQ PCF API specific statistics
1299
+
######PCF requests
1085
1300
These metrics are collected via sending direct PCF commands to queue manager.
0 commit comments