Self Monitoring Deployment Event:Monitor Instances count 33311 has exceeded the threshold limit on the TrueSight Infrastructure Management Server |
We read the configuration value for TSIM process based on load on TSIM Server. By reading the “MaxHeap” property value from the pnrate.conf, pnjserver.conf, pnagentcntl.conf files we identify the deployment type like SMALL, MEDIUM or LARGE. We have below threshold to check the count of device,monitor and attribute and once we cross the 50% of upper limit then we start notify via event so that admin can aware of it and this can be find in pronet.conf under TSIM/pw/pronto/conf folder pronet.deployment.selfmonitor.device.threshold.min=50 pronet.deployment.selfmonitor.device.threshold.max=90 pronet.deployment.selfmonitor.instance.threshold.min=50 pronet.deployment.selfmonitor.instance.threshold.max=90 pronet.deployment.selfmonitor.attribute.threshold.min=50 pronet.deployment.selfmonitor.attribute.threshold.max=90 pronet.deployment.selfmonitor.event.threshold.min=50 pronet.deployment.selfmonitor.event.threshold.max=90 Below is the properties to enable/disable this functionality with True and False value. pronet.deployment.selfmonitor.feature.enable Below is the approach for enhance self-monitoring so an alarm is generated if the number of monitored instances or attributes is approaching the upper limit for the environment. Based on the configuration setting in the TSIM Server Characteristic Small environment Medium environment Large environment Size of jserver default (2 GB) 4 GB 10 GB Size of rate default (2 GB) 4 GB 6 GB Size of agent controller default (2 GB) 4 GB 7 GB We read the configuration setting from BPPM server and identify the Small or Medium or Large deployment Based on the scheduler task once in an hour (configurable) we will trigger and validate the device, instances and attributes with count and will trigger the events once it reaches 90%(configurable) of the max limit. |