Dotnet GC Statistics Test

This test monitors the memory allocation activity of each ASP .Net server integrated with the IBM Integration Bus, in terms of heaps when objects are created and managed.

Target of the test : An IBM Integration Bus

Agent deploying the test : An internal/remote agent.

Outputs of the test : One set of results for each Execution group:decision service that is to be monitored

Configurable parameters for the test
Parameters	Description
Test period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The port on which the specified host listens.
JNDI Namespace Location	Indicate where the JNDI namespace has been created. For this, select one of the following options: File or LDAP. Select File if the JNDI namespace is created in the same location as that of the IIB server.
SSL	If you have chosen LDAP as the JNDI Namespace Location wherein the LDAP server communicating with the IIB server that is to be monitored is an SSL-enabled server, then set the SSL flag to Yes. By default, this flag is set to No.
User DN and Password	Here, provide the credentials of the Active Directory user created as explained in Creating a user in the Active Directory server, if the target IIB server is monitored in an agentless manner. If the IIB server is to be monitored in an agent based manner, specify none against these parameters.
Confirm Password	Confirm the Password by retyping it in this text box.
JNDI Provider URL	Specify the URL that was specified as the provider URL while creating the initial context. To know the Provider URL, refer to Agent based monitoring of the IIB server if you choose to monitor the target IIB server in an agent based manner and Agentless Monitoring of the IIB server if you chose to monitor the target IIB server in an agentless manner.
TopicConnectionFactory	Specify the name of the connection factory in this text box. If you have chosen to monitor the target IIB server in an agent-based manner, refer to Creating a Connection Factory and if you have chosen to monitor the target IIB server in an agentless manner, refer to Creating a Connection Factory.
JMS Resource Stats	Specify the name of the JMS destination that you have created for storing the Resource statistics. If you chose to monitor the target IIB server in an agentless manner, refer to Creating the JMS Destinations and if you choose to monitor the target IIB server in an agent based manner, refer to Agent based monitoring of the IIB server.
JMS Flow Stats	Specify the name of the JMS destination that you have created for storing the Message flow statistics. If you chose to monitor the target IIB server in an agentless manner, refer to Creating the JMS Destinations and if you choose to monitor the target IIB server in an agent based manner, refer to Agent based monitoring of the IIB server.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Explicit GC count	Indicates the number of garbage collections that were forced by an external request for this server during the last measurement period.	Number
Generation 0 collections taken	Indicates the number of generation 0 objects (youngest; most recently allocated) that were garbage collected (Gen 0 GC) since the start of the application.	Number
Generation 1 collections taken	Indicates the number of generation 1 objects that have been garbage collected since the start of the application.	Number	Objects that survive are promoted to generation 2.
Generation 2 collections taken	Indicates the number of generation 2 objects that have been garbage collected since the start of the application.	Number	Generation 2 is the highest, thus objects that survive collection remain in generation 2. Generation 2 collections can be very expensive, especially if the size of the Generation 2 heap is huge.
Reserved in all heaps	Indicates the amount of memory in bytes that are reserved in all heaps.	MB
Generation zero heap size	Indicates the maximum amount of bytes that can be allocated in generation 0.	MB	A generation 0 garbage collection occurs when the allocations since the last collection exceed this size. The generation 0 size is tuned by the garbage collector and can change during the execution of the application. At the end of a generation 0 collection the size of the generation 0 heap is 0 bytes. This measure displays the size, in bytes, of allocations that invokes the next generation 0 garbage collection. This measure is updated at the end of a garbage collection, not at each allocation.
Generation one heap size	Indicates the amount of bytes in generation 1.	MB	Objects are not directly allocated in this generation; they are promoted from previous generation 0 garbage collections. This measure is updated at the end of a garbage collection, not at each allocation.
Generation two heap size	Indicates the amount of bytes in generation 2.	MB	Objects are not directly allocated in this generation; they are promoted from generation 1 during previous generation 1 garbage collections. This measure is updated at the end of a garbage collection, not at each allocation.
Largest object heap size	Indicates the current size of the largest object heap.	MB	Objects that are greater than approximately 85,000 bytes are treated as large objects by the garbage collector and are directly allocated in a special heap; they are not promoted through the generations. This counter is updated at the end of a garbage collection, not at each allocation.
Promoted from generation 0 to 1	Indicates the amount of memory that survived garbage collection and are promoted from generation 0 to generation 1.	MB	Objects that are promoted only because they are waiting to be finalized are not included in this measure. This measure displays the value observed at the end of the last garbage collection.
Promoted from generation 1 to 2	Indicates the amount of memory that survived garbage collection and are promoted from generation 1 to generation 2.	MB	Objects that are promoted only because they are waiting to be finalized are not included in this measure. This measure displays the value observed at the end of the last garbage collection. This measure is reset to 0 if the last garbage collection was a generation 0 collection only.