When a Threshold starts and it does not find a condition exception, it uses the information specified in the Check Interval field of the Timing tab to determine how often to check for the condition. The Check Interval defines the interval at which data will be sent to the Threshold from the Collector. For example, if this field is set to 30 seconds, the Threshold will check the collected data for the condition every 30 seconds. If it finds a condition exception, it uses the information specified in the Log Frequency fields to determine how often to log an ON EVENT message.
1. Does increasing the Check Interval from 10 to 30 seconds mean that Threshold will collect data for 30 seconds?
2. CPU # 4 (RemoteParocessId) from PVIEWS What is this?
Solved! Go to Solution.
For your question #1 the answer is Yes. The threshold will collect data every 30 seconds if you set the check interval to 30 seconds.
I don't understand your question #2. Can you explain what is "CPU #4"???
Based on our records you are from KCI which is IR's reseller responsible for Level 1 Support. And usually these are questions that Level 1 support should be able to answer.
With reference to your second question, this is the symbolic ID of the collector process (in this case, STCPU in CPU 4). This is what is supplying data to whatever is requesting it (it'll tell you what kind of request in the requester type field). This should be either 'ONLINE' for a display/dashboard request, 'DATABSE' or 'THRESHOLD'.
I checked once more what I know.
I will take this question and ask a new one again.
I ran three Thresholds (check insterval: 10 seconds).
10:00 Run Threshold 1 (Check Interval 10 seconds)
10:10 Run Threshold 2 (Check Interval 10 seconds)
10:20 Run Threshold 3 (Check Interval 10 seconds)
However, if you see three thresholds in the PrognosisViewUsage Record, LastIntervalTime displays the same time.
Even if I run Threshold at different times, is it merged from the network router and then separated according to the source of the requested data?
We already know the schedule function to specify the time.
Is there any other way?
That's correct, the view requests are merged into a single collection request that's made on the 10 second boundary. The reason for this is to make data collection more efficient and prevent the collector and IRNETRTR from consuming excessive resources on the system. The only way to separate the requests would be to use an odd value for the check interval like the example I've attached, where I've configured one threshold to use use a check interval of 7 secs and one to use 9 secs.
I saw CPU BUSY of IRNETRTR per 10 seconds through COMPRESSION (NETRTR, OFF)-> ON.
CPU BUSY has been reduced by 3%.
COMPRESSION (NETRTR, OFF) is known to compress and reduce network traffic.
Can using this have a relatively big impact on the CPU?
Is there any way to reduce network traffic?
Having looked at the planning phase in session one of this series, we will turn our focus to the readiness phase. The all important technical capabilities assessment, ensuring the network, endpoints and users are adequately prepared for the move.
Hear first hand from IR's Global Head of Information Systems and Technology, Jason Schwendinger, on how he has been tackling these issues.Join webinar