Thanks, that works. Now I'm getting a 2 for status as expected.
tedv
Posts
-
ServiceCheck.Custom parameters? -
ServiceCheck.Custom parameters?@victor said in ServiceCheck.Custom parameters?:
Hi!
ServiceCheck.Custom accepts two arguments - host name or IP address and port number. For example, to check port 8080 on address 10.1.2.3, use
ServiceCheck.Custom(10.1.2.3,8080)
All ServiceCheck.* parameters return the following values:
0 - success (server was connected and return expected response);
1 - invalid arguments was passed;
2 - cannot connect to server;
3 - bad server's response.Best regards,
VictorThanks Victor - that works.
However, when I (for testing purposed) make sure that the node can't reach the other host, the value of the DCI doesn't change, it just does not get updated anymore. So, I can't put a threshold on it?Example
My data collection does ServiceCheck.Custom(10.1.2.3,8080) - that gives 0 as response every 30 seconds (the interval).
When I trick the machine that it can't reach the other host (10.1.2.3), the value stays at 0 and the timestamp isn't updated.
Any suggestions?
Thanks,
Ted -
ServiceCheck.Custom parameters?Hi, I'm trying to monitor from a node if it can reach a TCP port on another machine.
The ServiceCheck.Custom appears to be the most logical data collection item.
However, I can't find a description of the parameters
What would be the parameters to check if for example port 8080 gives a response on IP 10.1.2.3 (it's not HTTP)
Thanks,
Ted