{"_id":"58749d24edcf9f2f00f9dfbc","project":"56a1f77442dfda0d00046285","category":{"_id":"56a20bdf8b2e6f0d0018ea84","pages":["56a20e302255370d00ad5ecb"],"project":"56a1f77442dfda0d00046285","__v":1,"version":"56a1f77542dfda0d00046288","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-22T11:00:47.207Z","from_sync":false,"order":3,"slug":"features","title":"Features"},"parentDoc":null,"__v":0,"version":{"_id":"56a1f77542dfda0d00046288","__v":9,"project":"56a1f77442dfda0d00046285","createdAt":"2016-01-22T09:33:41.397Z","releaseDate":"2016-01-22T09:33:41.397Z","categories":["56a1f77542dfda0d00046289","56a1fdf442dfda0d00046294","56a2079f0067c00d00a2f955","56a20bdf8b2e6f0d0018ea84","56a3e78a94ec0a0d00b39fed","56af19929d32e30d0006d2ce","5721f4e9dcfa860e005bef98","574e870be892bf0e004fde0d","5832fdcdb32d820f0072e12f"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"user":"56a1f7423845200d0066d71b","updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-01-10T08:36:52.848Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":9,"body":"If you provide any service on the internet from blogs to e-commerce sites and public API(s) it's important to **know your sites availability and response metrics**.\n\nIn some cases monitoring your application doesn't give enough information about how your end-to-end customers experience your site. It can happen that every application operates perfectly but for example one of your data centers in some regions has a network issue and your site is unavailable for a group of users in that region. Or maybe you just want to be sure that your site is fast and stable from **everywhere in the world**.\n\nTo support these needs Trace by RisingStack provides an uptime feature. Our uptime checker can give availability information and **detailed metrics from different regions** like Asia, Europe and America as well. \n\n## Collected metrics\n\n* **Uptime** *(availability in %)*\n* **Apdex** *(in 0-1 range)*\n* **Downtime** *(in minutes)*\n* **Number of errors** *(timeouts, bad status codes etc.)*\n* **Status code** of response\n* **Header size** *(in bytes)*\n* **Body size** *(in bytes)*\n* **Total response time** *(in milliseconds)*\n* Timing of **Name lookup** *(in milliseconds)*\n* Timing of **Connect** *(in milliseconds)*\n* Timing of **TLS Handshake** *(in milliseconds)*\n* Timing of **First Byte** *(in milliseconds)*\n* Timing of **Redirects** *(in milliseconds)*\n\n## Apdex\n\nTrace by RisingStack Uptime feature can collect and visualize the Apdex quality metrics of your sites or API. With Apdex you can easily see that the site fulfills your target response time requirements over time or not.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/fa44c47-uptime-apdex.png\",\n        \"uptime-apdex.png\",\n        2604,\n        1908,\n        \"#3792be\"\n      ],\n      \"caption\": \"Apdex metrics of a site over time\"\n    }\n  ]\n}\n[/block]\n### What is Apdex?\n\n\"Apdex (Application Performance Index) is an open standard developed by an alliance of companies. It defines a standard method for reporting and comparing the performance of software applications in computing. Its purpose is to convert measurements into insights about user satisfaction, by specifying a uniform way to analyze and report on the degree to which measured performance meets user expectations.\"  - https://en.wikipedia.org/wiki/Apdex\n\n## Total response time\n\nTrace by RisingStack can visualize total response time history and color it based on your expectation.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/1066e7b-uptime-total.png\",\n        \"uptime-total.png\",\n        2594,\n        1898,\n        \"#e3e5eb\"\n      ],\n      \"caption\": \"Total response time over time\"\n    }\n  ]\n}\n[/block]\n## Total response time distribution\n\nIt's essential to know what most of the users can expect in response time when they are visiting your site. To helping explore it Trace by RisingStack provides a histogram for it.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/b620df4-uptime-total-histogram.png\",\n        \"uptime-total-histogram.png\",\n        2598,\n        1906,\n        \"#e2e5ec\"\n      ],\n      \"caption\": \"Total response time distribution over time\"\n    }\n  ]\n}\n[/block]\n## Timing distributions\n\nIn some cases, our response timer is slower because of different networking issues. With Trace by Risingstack's uptime checker, you can see timing of: **DNS Lookup**, **TCP connect**, **TLS handshake**, **First Byte**, **Content Transfer** and **Redirects**\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/fb02d7f-uptime-timing-distribution-dns-lookup-tcp.png\",\n        \"uptime-timing-distribution-dns-lookup-tcp.png\",\n        2588,\n        1906,\n        \"#2a485c\"\n      ],\n      \"caption\": \"Distribution of time spent with DNS lookup and establishing TCP connection\"\n    }\n  ]\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/7e791c0-uptime-timing-distribution-content-transfer.png\",\n        \"uptime-timing-distribution-content-transfer.png\",\n        2588,\n        1904,\n        \"#2b536e\"\n      ],\n      \"caption\": \"Distribution of time spent with TLS Handshake and elapsed time until first byte arrived.\"\n    }\n  ]\n}\n[/block]\n## Currently supported regions\n\nWe are continuously working on supporting more and more regions in different data centers. \nHere is the list of the currently supported regions:\n\n* **Eastern Asia-Pacific**, Changhua County, Taiwan, Google Cloud\n* **Western Europe**, St. Ghislain, Belgium, Google Cloud\n* **Eastern US**, Berkeley County, South Carolina, Google Cloud\n* **Western US**, The Dalles, Oregon, Google Cloud\n\nDon't you find your favorite region? Let us know!\n\n## Target total\n\nTrace by RisingStack uses the target total user input to determinate that a response fulfills your expected requirements. We also calculate the site's Apdex value and colorize our charts based on the target total value.\n\n### What is a good target total?\n\nIt depends on your business and expectations, for some sites, it's okay to respond in a second while we expect some API(s) to be super fast and response in 20ms. There is no rule for it, but I can tell you, faster is usually better.\n\n## Timeout\n\nUptime checker waits 30 seconds before it marks a request as timeout issue.","excerpt":"Website and API availability checking and response metrics","slug":"uptime","type":"basic","title":"Uptime"}

Uptime

Website and API availability checking and response metrics

If you provide any service on the internet from blogs to e-commerce sites and public API(s) it's important to **know your sites availability and response metrics**. In some cases monitoring your application doesn't give enough information about how your end-to-end customers experience your site. It can happen that every application operates perfectly but for example one of your data centers in some regions has a network issue and your site is unavailable for a group of users in that region. Or maybe you just want to be sure that your site is fast and stable from **everywhere in the world**. To support these needs Trace by RisingStack provides an uptime feature. Our uptime checker can give availability information and **detailed metrics from different regions** like Asia, Europe and America as well. ## Collected metrics * **Uptime** *(availability in %)* * **Apdex** *(in 0-1 range)* * **Downtime** *(in minutes)* * **Number of errors** *(timeouts, bad status codes etc.)* * **Status code** of response * **Header size** *(in bytes)* * **Body size** *(in bytes)* * **Total response time** *(in milliseconds)* * Timing of **Name lookup** *(in milliseconds)* * Timing of **Connect** *(in milliseconds)* * Timing of **TLS Handshake** *(in milliseconds)* * Timing of **First Byte** *(in milliseconds)* * Timing of **Redirects** *(in milliseconds)* ## Apdex Trace by RisingStack Uptime feature can collect and visualize the Apdex quality metrics of your sites or API. With Apdex you can easily see that the site fulfills your target response time requirements over time or not. [block:image] { "images": [ { "image": [ "https://files.readme.io/fa44c47-uptime-apdex.png", "uptime-apdex.png", 2604, 1908, "#3792be" ], "caption": "Apdex metrics of a site over time" } ] } [/block] ### What is Apdex? "Apdex (Application Performance Index) is an open standard developed by an alliance of companies. It defines a standard method for reporting and comparing the performance of software applications in computing. Its purpose is to convert measurements into insights about user satisfaction, by specifying a uniform way to analyze and report on the degree to which measured performance meets user expectations." - https://en.wikipedia.org/wiki/Apdex ## Total response time Trace by RisingStack can visualize total response time history and color it based on your expectation. [block:image] { "images": [ { "image": [ "https://files.readme.io/1066e7b-uptime-total.png", "uptime-total.png", 2594, 1898, "#e3e5eb" ], "caption": "Total response time over time" } ] } [/block] ## Total response time distribution It's essential to know what most of the users can expect in response time when they are visiting your site. To helping explore it Trace by RisingStack provides a histogram for it. [block:image] { "images": [ { "image": [ "https://files.readme.io/b620df4-uptime-total-histogram.png", "uptime-total-histogram.png", 2598, 1906, "#e2e5ec" ], "caption": "Total response time distribution over time" } ] } [/block] ## Timing distributions In some cases, our response timer is slower because of different networking issues. With Trace by Risingstack's uptime checker, you can see timing of: **DNS Lookup**, **TCP connect**, **TLS handshake**, **First Byte**, **Content Transfer** and **Redirects** [block:image] { "images": [ { "image": [ "https://files.readme.io/fb02d7f-uptime-timing-distribution-dns-lookup-tcp.png", "uptime-timing-distribution-dns-lookup-tcp.png", 2588, 1906, "#2a485c" ], "caption": "Distribution of time spent with DNS lookup and establishing TCP connection" } ] } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/7e791c0-uptime-timing-distribution-content-transfer.png", "uptime-timing-distribution-content-transfer.png", 2588, 1904, "#2b536e" ], "caption": "Distribution of time spent with TLS Handshake and elapsed time until first byte arrived." } ] } [/block] ## Currently supported regions We are continuously working on supporting more and more regions in different data centers. Here is the list of the currently supported regions: * **Eastern Asia-Pacific**, Changhua County, Taiwan, Google Cloud * **Western Europe**, St. Ghislain, Belgium, Google Cloud * **Eastern US**, Berkeley County, South Carolina, Google Cloud * **Western US**, The Dalles, Oregon, Google Cloud Don't you find your favorite region? Let us know! ## Target total Trace by RisingStack uses the target total user input to determinate that a response fulfills your expected requirements. We also calculate the site's Apdex value and colorize our charts based on the target total value. ### What is a good target total? It depends on your business and expectations, for some sites, it's okay to respond in a second while we expect some API(s) to be super fast and response in 20ms. There is no rule for it, but I can tell you, faster is usually better. ## Timeout Uptime checker waits 30 seconds before it marks a request as timeout issue.