TIBCO Metrics

Introduction

This is TIBCO Metrics for AciveSpaces Transactions (AST). It allows applications to gather metrics in one place and provide access to those metrics from the administrator, flushing to a file or via SNMP get.

Please see the enclosed javadoc.

Metric types

The following metric types are supported

RateMetric

The rate metric measures and reports based on rates. This can be used, for example, to monitor and report messages per second. Rate metrics can be incremented or set under application control.

A rate metric also has a number of samples to store and the time between each sample.

A given rate metric includes one or more result of the business operation. This can be used to compare the different possible outcomes of the same operations - for example, an inbound message passing of failing.

GaugeMetric

The gauge metric measures and reports a single value. This can be used, for example, to report a balance. Gauge metrics can be incremented or set under application control.

Like the rate metric, a gauge metric also supports one or more results of the business operation.

GaugeTableMetric

The gauge table metric measures and reports a table of values. This can be used, for example, to report a balance per account. A gauge in the table of metrics can be incremented or set under application control.

Like the gauge metric, a gauge table metric also supports one or more results of the business operation.

CardinalityMetric

The cardinality metric measures and reports a single value obtained from the cardinality of a AST managed object class.

ExternalMetric

The external metric does not store the value itself, instead it relies on external class to provide the counters which this metric fetches upon request. It is also possible to reset the external counter using this metric.

This metric can be used to expose counters defined in external components.

One example of usage is the system metric, described below.

SystemMetric

The system metric is an external metric that is used to report system (machine) dependent metrics, such as CPU usage, JVM Memory usage, Shared memory usage, etc. For list of supported metrics see SystemMetric javadoc.

Registering metrics

Applications can invoke the metrics API to register metrics in a hierarchy. Metrics are contained within a group and groups are contained within an application. For example :-

Manager.registerApplication("Application", "My Super App");
Manager.registerGroup("Group", "My Super Group", "Application");
Manager.registerRateMetric("Transactions", new String[] { "Pass", "Fail" }, "Inbound messages", "Group", 10, 2000);
Manager.registerGaugeMetric("Balance", new String[] { "Total", }, "Current Balance", "Group");
Manager.registerGaugeTableMetric("Balance", new String[] { "Total", }, "Current Balance", "Group");
Manager.registerCardinalityMetric("Subscribers", "Active Subscribers", "Group", "com.tibco.testmetrics.Subscriber");

Optional indexes may be supplied - these are used derive the SNMP OID's and may be used for other purposes in the future.

Manager.registerApplication("Application", "My Super App", 1);
Manager.registerGroup("Group", "My Super Group", "Application", 1);
Manager.registerRateMetric("Transactions", new String[] { "Pass", "Fail" }, "Inbound messages", "Group", 10, 2000, 1, new long[] {1, 2});
Manager.registerGaugeMetric("Balance", new String[] { "Total", }, "Current Balance", "Group", 2, new long[] {1});
Manager.registerCardinalityMetric("Subscribers", "Active Subscribers", "Group", "com.tibco.testmetrics.Subscriber", 3);

System metrics are registered the same as gauge metrics. However external class name that implements the counters must be supplied as well.

Manager.registerGaugeMetric("CPU", new String[] { "Usage", }, "CPU usage", "System", 0, new long[] {0}, "", "com.tibco.metrics.SystemMetric");
Manager.registerGaugeMetric("Memory", new String[] { "JVM Memory", "Shared memory" }, "Memory usage", "System", 1, new long[] {0, 1}, "", "com.tibco.metrics.SystemMetric");

Updating metrics

Applications can invoke the metrics API to update metrics. For example :-

Manager.incrementMetric("Transactions", "Pass", 10);
Manager.incrementMetric("Transactions", "Fail", 1);
Manager.incrementMetric("Balance", "Total", 1);
Manager.incrementMetric("Balance", "Total", "Halifax", 1); // for GaugeTable metric, Halifax is the entry name
Manager.setMetric("Balance", "Total", 10000);
Manager.setMetric("Balance", "Total", "Halifax", 10000); // for GaugeTable metric, Halifax is the entry name

External metrics however cannot be updated like this. Instead, the class that implements the counters does the updates and external metric just fetch the value from the counters class.

Reporting by administrator

The command-line tool, administrator, can report the metrics. Administrator commands can, of course, also be invoked by the AST GUI ASTA.

Displaying the configured applications

administrator display metrics
Application Name Application Description
Application My Super App

Displaying the configured groups

administrator display metrics application=Application
Group Name Group Description
Group My Super Group
System System metrics Group

Displaying the configured metrics

administrator display metrics group=Group
Metric Name Metric Type Metric Result Metric Description
Transactions Rate Fail Inbound Messages
Transactions Rate Pass Inbound Messages
Balance Gauge Total Current Balance
Subscribers Cardinality Cardinality Active Subscribers
administrator display metrics group=System
Metric Name Metric Type Metric Result Metric Description
Memory Gauge JVM Memory Memory usage
Memory Gauge Shared memory Memory usage
CPU Gauge Usage CPU usage

Displaying a rate metric

administrator display metrics name=Transactions
Time Pass Fail
19:23:53 0 0
19:23:55 0 0
19:23:57 0 0
19:23:59 0 0
19:24:01 0 0
19:24:03 0 0
19:24:05 0 10
19:24:07 5 3
19:24:09 1 3
19:24:11 1 3

Displaying a gauge metric

administrator display metrics name=Balance
Total
1

Displaying a cardinality metric

administrator display metrics name=Subscribers
Cardinality
23

Reporting by JMX

Since the metrics are available via administrator, they can also be displayed on a JMX console - for example, jconsole. On startup, the AST application displays the JMX connection details :-

INFO: astdeploy.jar version: [TIBCO ActiveSpaces(R) Transactions 2.1.1 (build 120106)] starting at [Sat Mar 31 21:38:36 BST 2012]
INFO: node version: [TIBCO ActiveSpaces(R) Transactions 2.1.2 (build 120330)]
INFO: Starting application [com.kabira.maven.Runner] ...
INFO: AST component [com.kabira.maven.Runner] started on JVM [com_kabira_maven_Runner0].
INFO: JMX Management Service started at:
        plordw510:2099
        192.168.175.10:2099
        service:jmx:rmi:///jndi/rmi://plordw510:2099/jmxrmi

The JMX client can use this connection string to connect to the running application (note that valid credentials must be supplied) and the administrator commands run. See below for an example.

JConsole

Reporting by web console

The metrics component comes with a web jar archive to give access to the metrics via the ASTA GUI.

After the domain manager is started, the web jar file should be extracted in the htdocs directory. This depends, of course, where the domainmanager is installed.

$ cd nodes/domainmanager/apache/htdocs/
$ jar -xf metrics_1.0.0-SNAPSHOT_web.jar

The web console is then available by adding ui/metrics.html to the URL of the ASTA GUI.

$ firefox http://127.0.0.1:8080/ui/metrics.html

Note that not all browsers and browser versions are supported. Tested is firefox 3.6.28.

ASTA

Exposing metrics via SNMP GET

Metrics can be exposed via SNMP GET.

Applications could expose metrics by calling API which will create and start MetricsSnmpAgent:

agent = new MetricsSnmpAgent("0.0.0.0/12001");
agent.start();

After this point, metrics are exposed via SNMP. Object identifiers are based on enterprises 2000 with the remaining defined by the index specified when the metrics are created.

Result can be queried for example using command-line snmpwalk:

$ snmpwalk -v2c -c public localhost:53955 enterprises.2000
SNMPv2-SMI::enterprises.2000.1.1.1.1.1.0 = Counter64: 4325
SNMPv2-SMI::enterprises.2000.1.1.1.1.2.0 = Counter64: 4425
SNMPv2-SMI::enterprises.2000.1.1.1.1.3.0 = Counter64: 4525
SNMPv2-SMI::enterprises.2000.1.1.1.1.4.0 = Counter64: 4625
SNMPv2-SMI::enterprises.2000.1.1.1.1.5.0 = Counter64: 4725
SNMPv2-SMI::enterprises.2000.1.1.1.1.6.0 = Counter64: 4825
SNMPv2-SMI::enterprises.2000.1.1.1.1.7.0 = Counter64: 4925
SNMPv2-SMI::enterprises.2000.1.1.1.1.8.0 = Counter64: 5025
SNMPv2-SMI::enterprises.2000.1.1.1.1.9.0 = Counter64: 5125
SNMPv2-SMI::enterprises.2000.1.1.1.1.10.0 = Counter64: 2600
SNMPv2-SMI::enterprises.2000.1.1.1.2.1.0 = Counter64: 8650
SNMPv2-SMI::enterprises.2000.1.1.1.2.2.0 = Counter64: 8850
SNMPv2-SMI::enterprises.2000.1.1.1.2.3.0 = Counter64: 9050
SNMPv2-SMI::enterprises.2000.1.1.1.2.4.0 = Counter64: 9250
SNMPv2-SMI::enterprises.2000.1.1.1.2.5.0 = Counter64: 9450
SNMPv2-SMI::enterprises.2000.1.1.1.2.6.0 = Counter64: 9650
SNMPv2-SMI::enterprises.2000.1.1.1.2.7.0 = Counter64: 9850
SNMPv2-SMI::enterprises.2000.1.1.1.2.8.0 = Counter64: 10050
SNMPv2-SMI::enterprises.2000.1.1.1.2.9.0 = Counter64: 10250
SNMPv2-SMI::enterprises.2000.1.1.1.2.10.0 = Counter64: 5200
SNMPv2-SMI::enterprises.2000.1.1.2.1.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.1.3.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.1.4.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.2.1.1.1.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.2.1.1.2.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.2.1.1.3.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.2.1.2.1.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.2.1.2.2.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.2.1.2.3.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.2.2.1.0 = Counter64: 0
SNMPv2-SMI::enterprises.2000.1.2.2.2.0 = Counter64: 1
SNMPv2-SMI::enterprises.2000.1.2.2.3.0 = Counter64: 0

MIB

Once the metrics are created, the MIB may be exported using :-

$ administrator adminport=xxxx generatemib metrics

For example :-

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
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
APPLICATION1 DEFINITIONS ::= BEGIN
 
-- vim: set syntax=mib foldmethod=marker noet :
--
-- Generated MIB for My Super App (Application1)
--
 
IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Counter64, enterprises FROM SNMPv2-SMI
    tibco FROM THREEGPPFRAMEWORK
    ;
 
application1 MODULE-IDENTITY
    LAST-UPDATED "201901291140Z"
    ORGANIZATION "www.tibco.com"
    CONTACT-INFO "www.tibco.com"
    DESCRIPTION "My Super App"
    REVISION "201901291140Z"
    DESCRIPTION "exported"
    ::= { tibco 1 }
 
 
--
-- Group Group2
--
 
group2 OBJECT IDENTIFIER ::= { application1 2 }
group2-ccr OBJECT IDENTIFIER ::= { group2 1 }
ccr-fail OBJECT IDENTIFIER ::= { group2-ccr 2 }
ccr-fail-t0 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: CCR Messages
         Result: Fail
         Value: Rate per second at now - 2 seconds"
    DEFVAL { 0 }
    ::= { ccr-fail 1 }
ccr-fail-t1 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: CCR Messages
         Result: Fail
         Value: Rate per second at now - 1 seconds"
    DEFVAL { 0 }
    ::= { ccr-fail 2 }
ccr-fail-t2 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: CCR Messages
         Result: Fail
         Value: Rate per second at now - 0 seconds"
    DEFVAL { 0 }
    ::= { ccr-fail 3 }
ccr-pass OBJECT IDENTIFIER ::= { group2-ccr 1 }
ccr-pass-t0 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: CCR Messages
         Result: Pass
         Value: Rate per second at now - 2 seconds"
    DEFVAL { 0 }
    ::= { ccr-pass 1 }
ccr-pass-t1 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: CCR Messages
         Result: Pass
         Value: Rate per second at now - 1 seconds"
    DEFVAL { 0 }
    ::= { ccr-pass 2 }
ccr-pass-t2 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: CCR Messages
         Result: Pass
         Value: Rate per second at now - 0 seconds"
    DEFVAL { 0 }
    ::= { ccr-pass 3 }
group2-rar OBJECT IDENTIFIER ::= { group2 2 }
rar-failed OBJECT-TYPE
    SYNTAX Counter64
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: RAR messages
         Result: Failed
         Value: Current counter value"
    DEFVAL { 0 }
    ::= { group2-rar 3 }
rar-pass OBJECT-TYPE
    SYNTAX Counter64
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: RAR messages
         Result: Pass
         Value: Current counter value"
    DEFVAL { 0 }
    ::= { group2-rar 2 }
rar-total OBJECT-TYPE
    SYNTAX Counter64
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: RAR messages
         Result: Total
         Value: Current counter value"
    DEFVAL { 0 }
    ::= { group2-rar 1 }
 
--
-- Group Group
--
 
group OBJECT IDENTIFIER ::= { application1 1 }
group-transactions OBJECT IDENTIFIER ::= { group 1 }
transactions-fail OBJECT IDENTIFIER ::= { group-transactions 2 }
transactions-fail-t0 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Fail
         Value: Rate per second at now - 4 seconds"
    DEFVAL { 0 }
    ::= { transactions-fail 1 }
transactions-fail-t1 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Fail
         Value: Rate per second at now - 3 seconds"
    DEFVAL { 0 }
    ::= { transactions-fail 2 }
transactions-fail-t2 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Fail
         Value: Rate per second at now - 2 seconds"
    DEFVAL { 0 }
    ::= { transactions-fail 3 }
transactions-fail-t3 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Fail
         Value: Rate per second at now - 1 seconds"
    DEFVAL { 0 }
    ::= { transactions-fail 4 }
transactions-fail-t4 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Fail
         Value: Rate per second at now - 0 seconds"
    DEFVAL { 0 }
    ::= { transactions-fail 5 }
transactions-pass OBJECT IDENTIFIER ::= { group-transactions 1 }
transactions-pass-t0 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Pass
         Value: Rate per second at now - 4 seconds"
    DEFVAL { 0 }
    ::= { transactions-pass 1 }
transactions-pass-t1 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Pass
         Value: Rate per second at now - 3 seconds"
    DEFVAL { 0 }
    ::= { transactions-pass 2 }
transactions-pass-t2 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Pass
         Value: Rate per second at now - 2 seconds"
    DEFVAL { 0 }
    ::= { transactions-pass 3 }
transactions-pass-t3 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Pass
         Value: Rate per second at now - 1 seconds"
    DEFVAL { 0 }
    ::= { transactions-pass 4 }
transactions-pass-t4 OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Inbound Messages
         Result: Pass
         Value: Rate per second at now - 0 seconds"
    DEFVAL { 0 }
    ::= { transactions-pass 5 }
group-balance OBJECT IDENTIFIER ::= { group 1 }
balance-total OBJECT-TYPE
    SYNTAX Counter64
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Current Balance
         Result: Total
         Value: Current counter value"
    DEFVAL { 0 }
    ::= { group-balance 1 }
subscribers-cardinality OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: Active Subscribers
         Value: Number of com.tibco.testmetrics.Subscriber objects"
    DEFVAL { 0 }
    ::= { group 5 }
junkclass-cardinality OBJECT-TYPE
    SYNTAX Gauge
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
        "Group: My Super Group
         Metric: junk
         Value: Number of com.nothing objects"
    DEFVAL { 0 }
    ::= { group 4 }
 
END

Once this MIB is installed, snmpwalk can make use of this information :-

$ snmpwalk -v2c -c public localhost:53955 -m APPLICATION1 enterprises.2000
APPLICATION1::transactions-pass-t0.0 = Counter64: 26625
APPLICATION1::transactions-pass-t1.0 = Counter64: 26725
APPLICATION1::transactions-pass-t2.0 = Counter64: 26825
APPLICATION1::transactions-pass-t3.0 = Counter64: 26925
APPLICATION1::transactions-pass-t4.0 = Counter64: 27025
APPLICATION1::transactions-pass-t5.0 = Counter64: 27125
APPLICATION1::transactions-pass-t6.0 = Counter64: 27225
APPLICATION1::transactions-pass-t7.0 = Counter64: 27325
APPLICATION1::transactions-pass-t8.0 = Counter64: 27425
APPLICATION1::transactions-pass-t9.0 = Counter64: 27525
APPLICATION1::transactions-fail-t0.0 = Counter64: 53250
APPLICATION1::transactions-fail-t1.0 = Counter64: 53450
APPLICATION1::transactions-fail-t2.0 = Counter64: 53650
APPLICATION1::transactions-fail-t3.0 = Counter64: 53850
APPLICATION1::transactions-fail-t4.0 = Counter64: 54050
APPLICATION1::transactions-fail-t5.0 = Counter64: 54250
APPLICATION1::transactions-fail-t6.0 = Counter64: 54450
APPLICATION1::transactions-fail-t7.0 = Counter64: 54650
APPLICATION1::transactions-fail-t8.0 = Counter64: 54850
APPLICATION1::transactions-fail-t9.0 = Counter64: 55050
APPLICATION1::balance-total.0 = Counter64: 0
APPLICATION1::junkclass-cardinality.0 = Counter64: 0
APPLICATION1::subscribers-cardinality.0 = Counter64: 0
APPLICATION1::ccr-pass-t0.0 = Counter64: 0
APPLICATION1::ccr-pass-t1.0 = Counter64: 0
APPLICATION1::ccr-pass-t2.0 = Counter64: 0
APPLICATION1::ccr-fail-t0.0 = Counter64: 0
APPLICATION1::ccr-fail-t1.0 = Counter64: 0
APPLICATION1::ccr-fail-t2.0 = Counter64: 0
APPLICATION1::rar-total.0 = Counter64: 0
APPLICATION1::rar-pass.0 = Counter64: 1
APPLICATION1::rar-failed.0 = Counter64: 0

Graphical MIB browsers can be used as well.

MIB Browser

Exporting metrics to CSV

Metrics can be exported to a CSV file using administrator command.

This is useful if one needs to review differences in metrics/MIB during lifecycle of a project.

The output CSV file is named application name + .csv. The name of the file is also listed in the output of administrator command and it is generated inside the node directory.

Example:

$ administrator adminport=xxx exportcsv metrics
Result = CSV for metrics of application APPLICATION saved in APPLICATION.csv in node directory.

Example of generated CSV file:

<<Group Name>>, <<Group Description>>, <<Metric Name>>, <<Metric Description>>, <<Metric Type>>, <<Metric SNMP Type>>, <<Metric Result>>, <<OID>>
<<RAT-Type>>, <<Metrics related to RAT-Type>>, , , , , ,
, , CCRU RAT-Type, Number of CCRU messages per RAT-Type, GAUGE, Counter64, RAT-Type:1, 1.3.6.1.4.1.2000.1.11.2.4
, , CCRU RAT-Type, Number of CCRU messages per RAT-Type, GAUGE, Counter64, RAT-Type:0, 1.3.6.1.4.1.2000.1.11.2.3
...
<<P-CSCFs>>, <<Metrics related to P-CSCFs>>, , , , , ,
, , P-CSCF2, Number of diameter messages for P-CSCF2, GAUGE, Counter64, RxRAR:Total, 1.3.6.1.4.1.2000.1.10.2.12
, , P-CSCF2, Number of diameter messages for P-CSCF2, GAUGE, Counter64, RxRAR:Fail, 1.3.6.1.4.1.2000.1.10.2.11
, , P-CSCF2, Number of diameter messages for P-CSCF2, GAUGE, Counter64, RxRAR:Pass, 1.3.6.1.4.1.2000.1.10.2.10
...
<<P-GWs>>, <<Metrics related to PDN Gateways>>, , , , , ,
, , P-GW4, Number of diameter messages for P-GW4, GAUGE, Counter64, RAR:Total, 1.3.6.1.4.1.2000.1.9.4.12
, , P-GW4, Number of diameter messages for P-GW4, GAUGE, Counter64, RAR:Fail, 1.3.6.1.4.1.2000.1.9.4.11
, , P-GW4, Number of diameter messages for P-GW4, GAUGE, Counter64, RAR:Pass, 1.3.6.1.4.1.2000.1.9.4.10
...
<<User Data>>, <<Metrics related to user data>>, , , , , ,
, , Rx User Sessions, Number of Rx user sessions, CARDINALITY, Counter64, Cardinality, 1.3.6.1.4.1.2000.1.1.3.0
, , User Profiles, Number of user profiles, CARDINALITY, Counter64, Cardinality, 1.3.6.1.4.1.2000.1.1.2.0
, , User Sessions, Number of user sessions, CARDINALITY, Counter64, Cardinality, 1.3.6.1.4.1.2000.1.1.1.0