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

The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web.

Hypertext is structured text that uses logical links (hyperlinks) between nodes containing text. HTTP is the protocol to exchange or transfer hypertext. Read more on Wikipedia.

HTTPS (also called HTTP over TLS, HTTP over SSL and HTTP Secure is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security or its predecessor, Secure Sockets Layer. The main motivation for HTTPS is authenticationof the visited website and protection of the privacy and integrity of the exchanged data. Read more on Wikipedia.

Implemented features

HTTP(S) protocol allows you to check your website availability with HTTP(S) request and status codes. HTTP protocol provides standard status codes where code 200 means success and e.g 404 means page not found.

Verity if you essential website is available.

Protocol settings

Pulse - Monitoring Tool for JIRA provide availability URL request to the server. You can define:

  • tested URL adess,
  • "correct" response time,
  • success service status strategy,
  • timeout.

If timeout is reached, and you still do NOT have response it means that server is down.
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.

Examples

Below you can find sample of HTTP(S) protocol configuration in PULSE - Monitoring Tool for JIRA.

There are few steps to take HTTP(S) service test.They include:

  • sending requested URL address to remote server,
  • gathering remote server's response,
  • analyze HTTP response code.

Test will be successful if any (in this case one) attempt finishes successfully. Timeout for each of attempt can't exceed 6 seconds (i.e. 6000 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