...
TQLConsole provides users ability to turn on/off TQLEngine monitoring services. There As of Release 1.0.5 there are two types of monitoring services that are currently provided (as of Release 1.0.5)..
a) Network Change Detection
b) TQLEngine Memory and other key parameters
The services menu is accessible from the profile dropdown link.
...
TQLEngine Key Parameters (Memory, Queue) Monitoring
In this section you see all the projects that are part of your account on TQLStudio project dashboard page
...
TQLEngine key runtime parameters can be monitored by enabling the monitoring service.
Some of the parameters that are monitored are:
| Parameter | Description |
|---|---|
| AlarmCount | TQL engine has internal memory management program. This program raises alarm when memory utilization is found to be continuously crossing the threshold. This variable displays the count of how many times Alarm has been triggered |
| AlarmLevel | This denotes the level of memory consumption reached by the engine at which Alarm was triggered. That means if AlarmLevel is 0.6 then it means Alarm was triggered when memory consumption had reached up to 60% |
| FreeChannel | This is the number of free / available Sockets or Channels in the system |
| FreeMemory | This is the available or free memory which JVM can still use without any issues |
| JarsIncluded | List of all the jars that are in CLASSPATH or included or leveraged by TQL engine |
| JavaVersion | Java version that is being used by TQL engine |
| MaxMemory | This is the size of maximum memory that is currently allocated to TQL engine or its JVM |
| MaxQueueCheck | This is an action which will be taken by the engine should any internal queue exceed maximum allowed size. Default action will give you a warning including queue name and size. Queue name corresponds to subscriber ID so you should be able to determine overloaded subscribers (i.e. subscribers which process jobs slower than new jobs are coming) |
| MaxQueueSize | This is maximum internal queue size. Internal queues are used to serialize background jobs like TQL reporting and topic publishing processing (i.e. each subscriber would have its own queue and process all publishing requests in order) |
| NioAcceptedSocketChannel | Number of Accepted SocketChannels. Higher is this number higher are the chances of memory leak. Hence monitoring this parameter can be crucial |
| NioServerSocketChannel | Number of channels that are listening for incoming TCP connections |
| NullChannel | Number of Socket Channels that are not yet instantiated |
| OS | Operating System, its version and architecture, on which TQL engine is hosted and running |
| ProcessImportance | This field is maintained by internal memory management program of TQL engine. It denotes the importance of processes involved TQL engine. This importance can range between 0.0 to 1.0. If this value is 0.4 then, all processes below 0.4 will be considered for garbage collection when its triggered due to Alarm going off |
| Processors | Number of logical Processors or CPUs with which engine is running |
| ServerIP | IP address of server on which TQL engine is hosted or running |
| ServerName | Name of the server or box hosting the engine |
| TCPclientInfo | This field provides information on TCP connections formed at client side, read and written bytes, total reads and writes and average time taken by the connection for reads |
| TCPserverInfo | This field provides information on TCP connections formed at server side, read and written bytes, total reads and writes and average time taken by the connection for reads |
| TotalChannels | This is total number of Sockets or Channels in the system |
| TotalMemory | Total memory out of which heap memory is picked by JVM |
| UsedMemory | Memory currently used by JVM or TQL engine |
| UserCountry | Country or location where TQL engine is running |
| UserDirectory | TQL_HOME directory for current user, from where TQL engine is running |
| UserLanguage | Language preferred and set by user on the system TQL is running |
| UserTimeZone | Time Zone where TQL engine is running |