<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ping on Netdata</title><link>https://www.netdata.cloud/tags/ping/</link><description>Recent content in Ping on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 17 Oct 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/ping/index.xml" rel="self" type="application/rss+xml"/><item><title>How to monitor HTTP endpoints</title><link>https://www.netdata.cloud/blog/http-endpoints/</link><pubDate>Mon, 17 Oct 2022 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/http-endpoints/</guid><description>&lt;p>The &lt;a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol">HTTP protocol&lt;/a> has become the de facto standard application layer protocol of the internet. From publicly available web sites and APIs to “inter-process” communications in REST based microservice architectures or large &lt;a href="https://en.wikipedia.org/wiki/Service-oriented_architecture">Service Oriented Architectures&lt;/a> based on &lt;a href="https://en.wikipedia.org/wiki/SOAP">SOAP&lt;/a>, you find HTTP being used again and again, due to its simplicity and our familiarity with it. How many protocols can you name that have &lt;a href="https://imgur.com/gallery/4KqWq">memes&lt;/a> for their status codes? Of course, such a popular protocol has endless pages written about how to properly monitor the services that rely on it, with many options specific to every use case.&lt;!--truncate--> What you will learn here is how to get your basics done in monitoring HTTP endpoints, so you can be up and running in a few minutes, monitoring all HTTP services in your &lt;a href="https://www.netdata.cloud/blog/future-of-infrastructure-monitoring/">entire infrastructure&lt;/a>. &lt;/p></description></item><item><title>How to monitor host reachability</title><link>https://www.netdata.cloud/blog/how-to-monitor-host-reachability/</link><pubDate>Mon, 10 Oct 2022 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/how-to-monitor-host-reachability/</guid><description>&lt;p>Most sysadmins and developers have at some point used a few of the popular &lt;a href="https://www.tecmint.com/linux-networking-commands" target="_blank" rel="noopener">Linux networking commands&lt;/a> or their Windows equivalents to answer the common questions of &lt;a href="https://www.netdata.cloud/blog/web-servers-and-their-performance/">host reachability&lt;/a> - that is, whether a host or service is reachable and how fast it responds.&lt;/p>
&lt;!--truncate-->
&lt;h2 id="common-approaches-to-reachability">Common approaches to reachability&lt;/h2>
&lt;p>One of the simplest, common checks, is to simply &lt;code>ping&lt;/code> a host to verify that it’s reachable from where you issue the command, and to see the total time it takes for the host to receive your request.&lt;/p></description></item></channel></rss>