cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Understanding the AMD Status section (RT components) of //CAS/modulestatus?advanced=1 output

jeremy_p_somers
Participant

Hi, Is there a document that describes how to interpret the RT section of results returned by the modulestatus?advanced=1 command? There appears to be a great level of detail here regarding AMD load however I need further information to allow me to read it.

10 REPLIES 10

adam_piotrowicz
Dynatrace Pro
Dynatrace Pro

Indeed, this section contains tons of information, but they are not documented.

Anyway, what interests you the most is:

  1. Packet receiver status section - you can see what kind of driver you have, what are driver's and interface stats.
  2. SSL DECRYPTION STATUS section where you can start troubleshooting problems with lack of data for SSL Decrypted Software Services.

The rest is low level information for Development.

Thanks Adam.

Adam,

Can you share further information about the AMD Memory section? Comparing two AMDs that I believed have the same configuration I note significant differences, so I am wondering where I need to investigate to work out why they are different. One of them shows this....

RT	AMD memory
RT Users: 197 (197 - 0) of 197 Limit: 100000
RT session id used:671 (762 - 91) sizeof:160
RT SimpleLogData used:0 (288 - 288) sizeof:24
RT ConvProxy used:146315 (7120230 - 6973915) sizeof:184
RT TCP anlzrs used:17522 (64958 - 47436) sizeof:712
RT TCP sessions used:40931 (4354259 - 4313328) sizeof:752
RT IcmpAnlzr used:620 (652 - 32) sizeof:304
RT IpAnlzr used:40 (59 - 19) sizeof:248
RT KerberosUdp anlzr used:1 (5 - 4) sizeof:264
RT OneUDPAnlzr used:13113 (31818 - 18705) sizeof:248
RT GenericUDPAnlzr used:649 (1145 - 496) sizeof:224
RT ZdataBaseRecord used:0 (4129 - 4129) sizeof:200
RT ZdataCompabilityRecord used:0 (68471 - 68471) sizeof:696
RT AutoDiscoveryTcp analyzers used:60578 (292838 - 232260) sizeof:176
RT AutoDiscoveryTcp sessions used:24969 (6917479 - 6892510) sizeof:576
RT AutoDiscoveryUdp analyzers used:59 (152 - 93) sizeof:176
RT AutoDiscoveryUdp sessions used:42 (212 - 170) sizeof:376
RT NotInRangeOneAnlzr used:66589 (2714958 - 2648369) sizeof:216
RT NotInRangeAnlzr used:64443 (242605 - 178162) sizeof:184
RT String cache size: 0
RT SMB Cache size: 0 , Kerberos Tickets Cache size: 9999 , SBuffer objects size: 0

The other shows this....

RT	AMD memory
RT Users: 243 (243 - 0) of 243 Limit: 100000
RT session id used:979 (1032 - 53) sizeof:160
RT Jdata Discovery Entry Records used:0 (7834 - 7834) sizeof:40
RT Distribution samples used:6143 (29052 - 22909) sizeof:168
RT SimpleLogData used:0 (120 - 120) sizeof:24
RT ConvProxy used:296926 (2937430 - 2640504) sizeof:184
RT Http hits used:592 (155307 - 154715) sizeof:432
RT Http hits used:7201 (1465159 - 1457958) sizeof:432
RT Wan aware -> Web hit sessions used:2079 (132481 - 130402) sizeof:1008
RT Web light hit sessions used:44232 (1044173 - 999941) sizeof:976
RT Web Light Hit Anlzrs used:24335 (62329 - 37994) sizeof:624
RT Wan aware -> Web hit anlzrs used:794 (2211 - 1417) sizeof:440
RT SQL query hit stats used:894 (115630 - 114736) sizeof:560
RT SQL query stats used:1541 (4409 - 2868) sizeof:288
RT DRDA anlzr used:2 (6 - 4) sizeof:848
RT DRDA session used:1 (230 - 229) sizeof:1672
RT TCP anlzrs used:14641 (43865 - 29224) sizeof:712
RT TCP sessions used:27061 (1199722 - 1172661) sizeof:752
RT IcmpAnlzr used:941 (986 - 45) sizeof:304
RT Ifmx anlzr used:2 (4 - 2) sizeof:848
RT Ifmx session used:0 (4 - 4) sizeof:1656
RT IpAnlzr used:38 (46 - 😎 sizeof:248
RT Orcl anlzr used:434 (852 - 418) sizeof:848
RT Orcl session used:4052 (11570 - 7518) sizeof:1792
RT SSL anlzrs used:17745 (46346 - 28601) sizeof:480
RT SSL pages used:10949 (58482 - 47533) sizeof:456
RT SSL sessions used:20006 (218489 - 198483) sizeof:1440
RT Tds anlzr used:13 (37 - 24) sizeof:848
RT Tds session used:0 (38 - 38) sizeof:1808
RT OneUDPAnlzr used:22600 (34761 - 12161) sizeof:248
RT GenericUDPAnlzr used:1687 (3262 - 1575) sizeof:224
RT SmtpData used:134 (9455 - 9321) sizeof:120
RT Smtp anlzr used:133 (897 - 764) sizeof:664
RT Smtp session used:134 (6443 - 6309) sizeof:2360

RT	SMB anlzr used:1 (1 - 0) sizeof:544
RT SMB session used:1 (1 - 0) sizeof:1920
RT CharTable used:134 (6443 - 6309) sizeof:4096
RT XML trans anlzr used:0 (39232 - 39232) sizeof:312
RT XML trans used:4 (100154 - 100150) sizeof:584
RT SOAP anlzr used:1327 (4240 - 2913) sizeof:904
RT SOAP session used:2574 (39232 - 36658) sizeof:2520
RT SOAP trans anlzr used:2574 (39232 - 36658) sizeof:312
RT SOAP trans anlzr cfg used:1327 (4240 - 2913) sizeof:96
RT SOAP trans used:2107 (198648 - 196541) sizeof:712
RT MySQL anlzr used:4 (9 - 5) sizeof:848
RT MySQL session used:0 (11 - 11) sizeof:1656
RT ZdataBaseRecord used:63 (6123 - 6060) sizeof:200
RT ZdataNonHitTcpRecord used:0 (1866 - 1866) sizeof:296
RT ZdataCompabilityRecord used:25703 (85572 - 59869) sizeof:696
RT ZdataDatabaseRecord used:352 (2761 - 2409) sizeof:624
RT ZdataAllOtherCompatibilityRecord used:1280 (4332 - 3052) sizeof:688
RT ZdataAllOtherDatabaseRecord used:94 (660 - 566) sizeof:616
RT ZdataSMBRecord used:0 (2 - 2) sizeof:656
RT LdapOneAnlzr used:32 (2927 - 2895) sizeof:1912
RT LdapAnlzr used:35 (271 - 236) sizeof:800
RT AutoDiscoveryTcp analyzers used:31318 (119785 - 88467) sizeof:176
RT AutoDiscoveryTcp sessions used:34380 (2670559 - 2636179) sizeof:576
RT AutoDiscoveryUdp analyzers used:25 (85 - 60) sizeof:176
RT AutoDiscoveryUdp sessions used:19 (95 - 76) sizeof:376
RT WebSingleHit used:3585 (155307 - 151722) sizeof:1184
RT WebLightHit used:7201 (1465159 - 1457958) sizeof:864
RT Zdata Lhttp records used:32384 (94457 - 62073) sizeof:528
RT Per-URI statistics used:32399 (70786 - 38387) sizeof:336
RT Zdata Lhttp all other records used:15461 (50184 - 34723) sizeof:408
RT web::Client used:62 (6908 - 6846) sizeof:288
RT web::Page used:302 (15466 - 15164) sizeof:344
RT web::KData used:119 (1251 - 1132) sizeof:160

RT	web::ZData used:480 (6604 - 6124) sizeof:584
RT YAHA JBoss hit analyzers used:362 (799 - 437) sizeof:432
RT YAHA JBoss hit session analyzers used:8098 (141763 - 133665) sizeof:792
RT Yaha::OperationStats used:620 (1682 - 1062) sizeof:392
RT ZdataParserNonHitTcpRecord used:72 (768 - 696) sizeof:304
RT String cache size: 166
RT SMB Cache size: 2 , Kerberos Tickets Cache size: 21 , SBuffer objects size: 8

wojciech_kurek
Inactive

Jeremy,

Information in the 'AMD Memory' section is not useful without knowledge about the AMD's internals and code. The metrics in this section are not memory indicators and do not relate to the AMD's memory usage directly.

In this particular case it looks like the first AMD lacks licenses and analyzes everything using the Generic decode.

Wojtek.

Thanks for this Wojtek. Good to understand that I shouldn't try to make direct sense of this information, though all the same it would be good to have this documented somewhere, even if that just says "don't try to make sense of it...." 🙂

From what you suggest it sounds like I should be opening a support ticket then? Both AMDs are loaded with the same license file (running under a PoC) so I am unclear where to go with this right now. Hopefully someone in support can work out what is going on once we do a webex. I might update this thread with the outcome, for the benefits of others later....

Jeremy

Yes, Support will help you with that.

I have logged the issue with Support (SUPDCRUM-10352) but so far no real joy. They did pick up I had a difference between AMDs with respect to excluded IP ranges, but when I fixed this I found it made no difference to my particular issue with.AMD Memory mappings.

I am struggling to understand why it is so difficult to do a comparison between AMD configurations though.

Is this a long term issue that has existed? How do customers cope who say have 3-10 AMDs running against a common CAS? Surely they have a requirement to keep their AMD configurations aligned? How are they achieving this task today? Support have suggested they have noticed multiple other misalignments but haven't come back to tell me what they are.

Jeremy