these two parameters operated independently.
If you want an alarm when the threads go over 250 and not when it is below 250 then you will set the max to 250 and leave the minium blank.
this will alarm on any value greater than 250.
With this option, you can not do a range value.
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 07-18-2019 10:31 AM
From: Siddharth Rai
Subject: Monitoring Processes (Process Probe)
Already tested other way around. No success. Still same error. If you see the message pool, it sends an alarm when thread count is less expected count. So whatever value we are setting up there, if the the process has less than expected (min thread) it would send an alarm.
While we want to have an alarm when value reaches 250 thread and upto 350
------------------------------
System Analyst
DXC Technology
Original Message:
Sent: 07-18-2019 08:33 AM
From: Gene HOWARD
Subject: Monitoring Processes (Process Probe)
It looks like you have your minimum and maximum values reversed in the probe setup.
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
Original Message:
Sent: 07-18-2019 06:58 AM
From: Siddharth Rai
Subject: Monitoring Processes (Process Probe)
the message pool is
------------------------------
System Analyst
DXC Technology
Original Message:
Sent: 07-18-2019 06:55 AM
From: Siddharth Rai
Subject: Monitoring Processes (Process Probe)
For one application we have currently set java process to have thread counts min 250 & max 350, so when thread count is lower than 250 or greater than 350 , an alarm is generated while we want that when thread count is between 250-350,Alarm should be generated. Can you please
(i have changed the values in max & min count boxes but no help)
can anybody please suggest me how can I do it accordingly ?..
------------------------------
System Analyst
DXC Technology
------------------------------