PULSE - Monitoring Tool for JIRA
Page tree
Skip to end of metadata
  • Created by Unknown User (robert.dzido@infodesign.pl) on Sep 06, 2016
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Protocol Overview

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source. The name comes from active sonar terminology that sends a pulse of sound and listens for the echo to detect objects under water, although it is sometimes interpreted as a backronym to packet Internet groper. Read more on Wikipedia.

Implemented features

ICMP protocol allows you to test if specified host is availables. During test always response time is mesuring but not always results are saved. 

Important

Some hosts may have defined firewall rules to block ICMP packets. In these situations we will NOT be notified about server response time and even if host is alive you will be informed host is down.

Protocol settings

Pulse - Monitoring Tool for JIRA provide availability host mechanism. You can define:

  • tested host address,
  • "correct" response time,
  • success service status strategy,
  • timeout.

If timeout is reached, and you still do NOT have response it means remote host is down or over firewall. Timeout protect your service against the eternal waiting for response - after that period your service will be notified about unavailability and next test will be executed. 

Service status strategy allows you to specify if:

  • all or any of attempts succeded,
  • we want use minimal, maximal or average test values to compare with yours.

Examples

Below you can see sample ICMP protocol configuration in Pulse - Monitoring Tool for JIRA.

There are few stepst to take ICMP services test. They include:

  • send ICMP packet to remote host,
  • remote host can NOT have ICMP packets blocking rule and have to be alive,
  • remote host have to send response,
  • average time of all attempts between your request and host response have to be lower than 20 (implicitly miliseconds).

Test will be successful if any of all (in this case any of five) attempt finishes successfully. Timeout for each of attempt can't exceed 0,5 second (i.e. 500 millis). In addition we checked "Collect test history" option which means all test results will be stored in database. It enables status history analysis. Stored detailed results are downloadable as *.csv file.




  • No labels