Elastic Uptime Monitoring 7.3.0 released with monitor summaries and detailed monitor duration charts

<p>We are pleased to announce a new release of Elastic Uptime Monitoring, version 7.3.0, available on the <a href="https://www.elastic.co/cloud/elasticsearch-service">Elasticsearch Service</a>, or as part of the <a href="https://www.elastic.co/downloads/">default distribution</a> of Elastic Stack.
</p><h2>Monitor Summaries</h2><p>When it comes to monitoring applications with Uptime, users often set up several geographically-dispersed monitors to get multiple perspectives on user experience.&nbsp;
</p><p>Monitor Summaries allow the user to see multiple Heartbeat results grouped in a single, expandable row per monitored endpoint. This visual representation in Uptime UI, called "Monitor summaries" improves the experience for users that are using multiple Heartbeat instances.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt23802e655f0d4614/5d386ae2e76cd34ed38d6e09/image2.gif" data-sys-asset-uid="blt23802e655f0d4614" alt="image2.gif">
</p><figcaption>Collapsable summaries<br><br><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt962f9f0af43026d7/5d386b0ce228515753543dd3/image3.png" data-sys-asset-uid="blt962f9f0af43026d7" alt="image3.png"></figcaption><p> In a closer look, as we expand a single endpoint, we can see the status of this endpoint monitored from 3 locations (California, New York, and the UK, which is currently down).
</p><h3>Monitors page</h3><p>Several UI improvements were made to the Monitors detail screen. The most significant one is the "Monitor duration" chart, where the user can see the duration of a single endpoint check across multiple locations, with the additional ability to filter per location as needed.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt5f01b5078e5082a8/5d386b22ffcdbf4f57a77af8/image1.png" data-sys-asset-uid="blt5f01b5078e5082a8" alt="image1.png"></p><h2>Want to see it in action?</h2><p>You can access the 7.3.0 Elastic Uptime application on the <a href="https://www.elastic.co/cloud/elasticsearch-service">Elasticsearch Service</a> on Elastic Cloud, or you can download it as part of the <a href="https://www.elastic.co/downloads/">default distribution</a> of the Elastic Stack. Download <a href="https://www.elastic.co/products/beats/heartbeat">Heartbeat</a>, follow the <a href="https://www.elastic.co/guide/en/beats/heartbeat/current/heartbeat-getting-started.html">instructions</a> on how to set it up, and start monitoring your applications and services today.
</p>

blog-banner-release-uptime.png

blog-thumb-release-uptime.png

Elastic Uptime Monitoring 7.3.0 released

Elastic Uptime 7.2.0 released with a more compact UI, custom ID and location support, as well integrations to quickly access Logs, Metrics, and APM Traces

<p>We are pleased to announce a new release of Elastic Uptime Monitoring, version 7.2.0, available on the <a href="https://www.elastic.co/cloud/elasticsearch-service">Elasticsearch Service</a>, or as part of the <a href="https://www.elastic.co/downloads/">default distribution</a> of Elastic Stack. In this release&nbsp;we added location support, so you can monitor and compare your site availability from where it matters most. We had also added bi-directional links between <a href="https://www.elastic.co/solutions/uptime-monitoring">Uptime</a> and <a href="https://www.elastic.co/solutions/logging">Logs</a>, <a href="https://www.elastic.co/solutions/metrics">Infrastructure</a>, and <a href="https://www.elastic.co/solutions/apm">APM</a>, to leverage the full observability capabilities of the Elastic Stack.
</p><h2>Location support</h2><p>When it comes to monitoring applications with Uptime, users often set up several geographically-dispersed monitors to get multiple perspectives on user experience. To analyze results from status checks from these different locations, it helps to have "location" as first-class meta-data. In 7.2 it is possible to add location information to Heartbeat data and the Uptime app in Kibana, simply by adding these four lines to heartbeat.yml file in the processors section.
</p><pre class="”prettyprint”">processors:
   - add_observer_metadata:
       geo:
         name: Heartbeat_location_name
</pre><p>Once Heartbeat sends its information to Elasticsearch you will immediately see the configured locations on our Overview and Monitor pages in the&nbsp;Uptime app in Kibana.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt8c4f1ce7e0abea89/5cffff5e900e486c1a96f2cf/uptime-7.2.0_2.jpg" data-sys-asset-uid="blt8c4f1ce7e0abea89" alt="uptime-7.2.0_2.jpg">
</p><p>More information on how to use <code>add_observer_metadata</code> processor can be found in <a href="https://www.elastic.co/guide/en/beats/heartbeat/master/add-observer-metadata.html#add-observer-metadata">Heartbeat documentation</a>.<br></p><h2>Integration with other observability solutions</h2><p>Got Logs? Metrics? APM Traces? In 7.2, we are doubling down on the value of using all of these apps together, by providing bi-directional links between Uptime and Logs, Infrastructure, and APM apps. These links provide an easy way to navigate to all solutions while preserving the right context.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt5e5a9c6d17b1f925/5cffffb6d5e132ea141ffbd2/uptime-7.2.0_1.jpg" data-sys-asset-uid="blt5e5a9c6d17b1f925" alt="uptime-7.2.0_1.jpg">
</p><p>When you start collecting logs, metrics, and APM traces on endpoints monitored by Uptime, you can navigate from familiar Uptime views to the rest of Observability UIs with a single click. This allows you to start with Uptime and expand to leveraging the full observability capabilities of the Elastic Stack for better troubleshooting and root cause analysis.
</p><h2>Ready to see it action?</h2><p><span></span>You can access the 7.2.0 Elastic Uptime application on the <a href="https://www.elastic.co/cloud/elasticsearch-service">Elasticsearch Service</a> on Elastic Cloud, or you can download it as part of the <a href="https://www.elastic.co/downloads/">default distribution</a> of the Elastic Stack. Download <a href="https://www.elastic.co/products/beats/heartbeat">Heartbeat</a>, follow the <a href="https://www.elastic.co/guide/en/beats/heartbeat/current/heartbeat-getting-started.html">instructions</a> on how to set it up, and start monitoring your applications and services today.
</p>

Elastic Uptime Monitoring 7.2.0 released

Service availability is one of the most important success metrics in service delivery. Proactive monitoring lets you discover issues sooner, for happier users

<p>We are happy to announce the general availability of the Elastic Uptime solution, new with Elastic Stack 6.7. To try it out, spin up a cluster in our <a href="https://www.elastic.co/cloud/elasticsearch-service">Elasticsearch Service</a> (on Elastic Cloud) or <a href="/solutions/uptime-monitoring">download</a> the Elastic Stack locally.
</p><h2>What is Uptime Monitoring?</h2><p>Service uptime is one of the most important success metrics in service delivery. If the service is down users cannot be successful, no matter how great the user experience is when the application is up. In the world of interconnected applications and microservices, operation teams face a wider footprint of critical endpoints to monitor, not all in their control. As a result, actively measuring, reporting, and alerting on service uptime and response time at scale is the cornerstone of any <a href="https://www.elastic.co/blog/observability-with-the-elastic-stack">observability</a> initiative.
</p><p>Measuring service availability starts with the basics. Are the hosts or containers underlying the applications responding to network pings? Is the application port responsible for communication accessible? Uptime checks get more intricate quickly. Is the website responsible for user interaction accessible by the users, and does the HTTP response delivered by the server contain the expected content? Is the set of internal APIs in a microservices architectures available and returning correct API responses? Are the 3rd party services the application rely on responding quickly?
</p><h2>Elastic Uptime</h2><p>The Elastic Uptime solution answers these questions easily and elegantly across all tiers and infrastructure components. Based on <a href="https://www.elastic.co/products/beats/heartbeat">Heartbeat</a>, an open source uptime monitor, Elastic Uptime is transparent, flexible, and developer-friendly. It can be deployed both inside and outside your organization's network to understand service uptime and response time characteristics from multiple network vantage points.
</p><p><img src="https://images.contentstack.io/v3/assets/bltf7afce26b89a5b33/bltc90e4553cc56043b/5c98da35e2a0d75e3346c76b/download" data-sys-asset-uid="blt91dde0dbfdd24acc" alt="image4.gif"><br>
</p><p>Combining uptime monitoring with logs, metrics, and APM trace data, with Elastic Stack as the operational datastore, organizations can bridge data silos and enable analyst workflows from high-level KPIs to detailed events. This speeds up troubleshooting and root cause analysis and further empowers observability initiatives. Elastic alerting and machine learning features provide proactive notification and anomaly detection capabilities on top of all this data in a consistent and data source agnostic way.
</p><p>In addition to ensuring the health of production applications, uptime monitoring can also help with quality assurance and continuous integration workflows. As your applications evolve and move through a set of planned changes, you can find out about problems in QA and Production before user traffic ever hits them. This speeds up product development cycles, while reducing risk of negative impact to your customers.
</p><h3>Collecting uptime information using Heartbeat</h3><p><a href="https://www.elastic.co/products/beats/heartbeat">Heartbeat</a> is an open source, lightweight shipper which was originally developed in close collaboration with our SRE team to measure the response time and availability of our <a href="https://www.elastic.co/cloud/">Elastic Cloud</a>&nbsp;services across multiple regions. The product was such a useful addition to our stack for logging and metrics analytics that we decided to release it, first as beta and then as a GA in 6.5.
</p><p>Heartbeat can operate from inside or outside of your network; all it needs is network access to the desired HTTP, TCP, or ICMP endpoint. Configuration is as simple as supplying Heartbeat with the list of URLs you want to monitor. Heartbeat executes periodic checks to verify whether the endpoint is up or down, then reports this information, along with other useful metrics, to Elasticsearch.
</p><p>In a typical customer deployment, we normally see Heartbeat deployed in multiple locations, to better simulate the end user experience coming from multiple vantage points. As soon as Heartbeat starts to run, it will check the list of endpoints you have configured, send the information to the Elastic Stack.
</p><p><br>
</p><p><img src="https://images.contentstack.io/v3/assets/bltf7afce26b89a5b33/blteb0e5345e3c73f5d/5c98da62ce43ee193330d773/download" data-sys-asset-uid="bltc88b33612199daf4" alt="image9.png">
</p><h3>Exploring monitor data in Elastic Uptime </h3><p>Now that we have the data, we can look at it in the Uptime application in Kibana.
</p><h4>Uptime Overview page</h4><h5>Endpoint status</h5><p>It really doesn't matter how many Heartbeat instances you've got. As long as they report their information to Elasticsearch, you will see an aggregated view across all your monitored endpoints. If you want to know how many of your endpoints are up or down this is the place to look.
</p><p><img src="https://images.contentstack.io/v3/assets/bltf7afce26b89a5b33/blt169585ce202170a4/5c98da75ce43ee193330d779/download" data-sys-asset-uid="blt0a3ca61e66e6b09a" alt="image5.png">
</p><h5>Status over time</h5><p>This chart provides the status across all monitored endpoints, over a period of time. The Y-axis is the number of the monitored endpoint, while the X-axis represent a period of a selected time.
</p><p><img src="https://images.contentstack.io/v3/assets/bltf7afce26b89a5b33/blt361d5acb7049d973/5c98da89aef178d33948bd2c/download" data-sys-asset-uid="bltf581761ed5273cd8" alt="image6.png">
</p><h5>Monitor status</h5><p>This table provides an up-to-date status on each individual endpoint that is monitored by Heartbeat
</p><p>Every line represents a single endpoint, with its related information, such as status (is the endpoint up or down), Last update (when did it report the latest information), Monitor name (if one was defined, otherwise the URL will be used), full URL, IP and status over time.
</p><p><br>
</p><p><img src="https://images.contentstack.io/v3/assets/bltf7afce26b89a5b33/blt4188eb54463e67b7/5c98da9dd06594542e96293f/download" data-sys-asset-uid="blt3d95f93fc8fb5fac" alt="image3.png">
</p><p>If you want to see the up-to-date status of each monitored endpoint, this is the where to look.
</p><h5>Error list</h5><p>If one of Heartbeat's monitors detects an error, Heartbeat will report it to Elasticsearch, and the error information will be presented in the error list table below. You will be able to see error code, error message, number of time this error occurred, and the error type.
</p><p><img src="https://images.contentstack.io/v3/assets/bltf7afce26b89a5b33/blt2a47b558e204773a/5c98dab549324e0c3a98e555/download" data-sys-asset-uid="bltb65733abcddaab34" alt="image8.png">
</p><h4>Uptime Monitor page</h4><p>When you click on a specific monitor – in the "Monitor Status" table, you will be redirected to the second page on this solution, the "Monitor page". This page would help you check a specific endpoint thoroughly.
</p><h5>Monitor duration and Check status</h5><p>The "Monitor duration" chart represent the response time over time (in milliseconds) for a specific endpoint, while the "Check status" chart represent the endpoint's availability over time.
</p><p><img src="https://images.contentstack.io/v3/assets/bltf7afce26b89a5b33/blt1c3e2b9861b655f6/5c98dac06f69e6812ec303ba/download" data-sys-asset-uid="blt5ca9b1be15652b33" alt="image7.png">
</p><h5>Check History<br></h5><p>This table provides a detailed view on each individual check. &nbsp;Every line in this table represents a single check that Heartbeat executes against a specific endpoint, you can filter to examine all checks or filter by up/down.
</p><p><img src="https://images.contentstack.io/v3/assets/bltf7afce26b89a5b33/blt5f4b79ef2ddffb08/5c98dad3aef178d33948bd36/download" data-sys-asset-uid="blt0ba59e988f7aec63" alt="image1.png">
</p><h3>Ad hoc analysis of uptime data using Kibana </h3><p>Heartbeat data is just another index in Elasticsearch. You can visualize Heartbeat data in Kibana for ad-hoc analysis. We provide a default dashboard to help you get started. To learn more about using Kibana for ad hoc analysis of Heartbeat data, please refer to the&nbsp;<a href="https://www.elastic.co/blog/uptime-monitoring-with-heartbeat-and-the-elastic-stack">Uptime Monitoring with Heartbeat and the Elastic Stack</a>&nbsp;blog.
</p><h3>Alerting on top of Uptime data</h3><p>You can create alerts on top of Uptime data using Watcher. Watcher is a powerful alerting and actions framework on top of Elasticsearch. Most simple threshold based alerts are easily created using the Watcher UI. For more advanced conditions and actions, you can also build a watch by working directly with the Watcher API. For a non-trivial example of an alert using uptime data, see the&nbsp;<a href="https://discuss.elastic.co/t/dec-19th-2018-en-heartbeat-configure-a-tls-expiration-notification-using-heartbeat/160503">Configure a TLS expiration notification using Heartbeat</a>&nbsp;blog&nbsp;to&nbsp;learn how to alert&nbsp;on invalid SSL certificates.
</p><h3>Observability using the Elastic Stack</h3><p>The 6.7 release also brings general availability of the Infrastructure and Logs solutions. In addition to <a href="https://www.elastic.co/solutions/apm">APM</a>, these solutions are a part of the broader '<a href="https://www.elastic.co/blog/observability-with-the-elastic-stack">observability' story using the Elastic Stack</a>.
</p><p><img src="https://images.contentstack.io/v3/assets/bltf7afce26b89a5b33/blt3e461d0c505ddcff/5c98dae749324e0c3a98e55b/download" data-sys-asset-uid="blta962e1544a97b739" alt="image2.png">
</p><h3>Done? We are just getting started!</h3><p>This is only the first phase of Uptime solution and we are not stopping here. In our upcoming releases, we will provide additional capabilities in terms of managing and configuring monitors. Until then, I hope you will use and enjoy this first release of Uptime monitoring, please feel free to reach out and to provide more feedback on our forum <a href="https://discuss.elastic.co/">discuss.elastic.co</a>.
</p>Uptime is available on Elastic Cloud <a href="https://www.elastic.co/cloud/elasticsearch-service">Elasticsearch Service</a> -- you can get started in just minutes with monitoring the uptime of your apps. Don't have an account? Sign up for a free <a href="https://www.elastic.co/cloud/elasticsearch-service/signup?storm=uptime-montitoring&elektra=blog">14-day trial</a> today.

Elastic Uptime Monitoring solution released

Heartbeat is generally available as of 6.5. It's about time you start monitoring your uptime (and downtime) all the time.

<p>With the <a href="/blog/elastic-stack-6-5-0-released">6.5</a> release of the Elastic Stack, we are happy to announce the general availability of <a href="/beats/heartbeat">Heartbeat</a>. Initially introduced in beta in January 2017, Heartbeat&nbsp;is a lightweight shipper&nbsp;— similar to the rest of our other Beats (<a href="/beats/metricbeat">Metricbeat</a>,&nbsp;<a href="/beats/filebeat">Filebeat</a>,&nbsp;<a href="/beats/winlogbeat">Winlogbeat</a>, etc.) — but it's&nbsp;designed for uptime monitoring.
</p><p>Heartbeat can operate from inside&nbsp;or outside of your network. All it needs is network access to the desired HTTP, TCP, or ICMP endpoint. Configuration is as simple as supplying Heartbeat with the list of URLs you want to monitor. Heartbeat executes periodic checks to verify whether the endpoint is up or down, then reports this information, along with other useful metrics, to Elasticsearch. This information is automatically displayed in pre-built Kibana dashboards for turnkey uptime monitoring.
</p><p>Let's take a closer look at how to set up and use Heartbeat with the Elastic Stack.
</p><h2>Installing Heartbeat</h2><p>To install Heartbeat, you will need to download and extract a pre-built executable for your platform. In this example, I will use macOS, however <a href="/guide/en/beats/heartbeat/6.5/heartbeat-installation.html">we support many other operating systems</a>, so you should use the commands that work with your system.
</p><p>Download and extract the latest version of Heartbeat:
</p><pre class="prettyprint">curl -l -O https://artifacts.elastic.co/downloads/beats/heartbeat/heartbeat-6.5.0-darwin-x86_64.tar.gz
tar xzvf heartbeat-6.5.0-darwin-x86_64.tar.gz
</pre><h2>Configuring Uptime Monitors</h2><p>In order for Heartbeat to know which service to check, it needs a list of URLs. This configuration is specified the <em>heartbeat.yml</em> file under the <em>/heartbeat</em> folder.&nbsp;Here is an example for multiple HTTP checks with Heartbeat, which run every 10 seconds:
</p><pre class="prettyprint"># Configure monitors
heartbeat.monitors:
- type: http
  # List or urls to query
  urls:
        - "https://www.elastic.co"
        - "https://discuss.elastic.co"
  # Configure task schedule
  schedule: '@every 10s'
</pre><p>In addition to the HTTP/S monitors, Heartbeat can perform TCP and ICMP checks so you can get better insight across different layers of your services. In Heartbeat we can also define additional layers of checks, for instance, with HTTP/S monitors we can check the response code, body and header. With TCP monitors we can define port checks and strings checks.
</p><pre class="prettyprint">heartbeat.monitors:
- type: http
# List or urls to query
  urls: ["http://localhost:9200"]
  # request details:
  check.request:
       method: GET
  check.response:
       body: "You Know, for Search"
# Configure task schedule
  schedule: '@every 10s'
</pre><p>Here is an example for an HTTP body check, where Heartbeat is looking for the string “You Know, for Search” at http://localhost:9200 (the only URL specified in the config).
</p><p>On all Heartbeat monitors, we can define additional parameters such as <code>name</code>, <code>timeout</code> and <code>schedule</code>. You can find complete configuration instructions on the <a href="/guide/en/beats/heartbeat/6.5/configuration-heartbeat-options.html">Configuring Heartbeat</a> documentation.
</p><p>The final step in the configuration is to setup Heartbeat outputs (where to send the data to). Among the supported outputs are self-managed Elasticsearch cluster, Elastic Cloud, Logstash and more.&nbsp;In this example, I am sending Heartbeat data into my local Elasticsearch instance &nbsp;(“localhost:9200”):
</p><pre class="prettyprint">output.elasticsearch:
# Array of hosts to connect to.
  hosts: ["localhost:9200"]
 # Optional protocol and basic auth credentials.
 #protocol: "https"
 username: "elastic"
  password: "changeme"
</pre><p>You can find an example file with the full configuration, in the <em>heartbeat.reference.yml</em> file.
</p><h2>Starting Heartbeat for the First Time</h2><p>Heartbeat comes with prebuilt dashboards that provide a lot of value out of the box. Set up the dashboards and run Heartbeat using these commands:
</p><p><strong>To set up Heartbeat dashboards in Kibana:</strong> (optional, and only needs to be run once)
</p><pre class="prettyprint">./heartbeat setup --dashboards
</pre><p><strong>To run Heartbeat:</strong>
</p><pre class="prettyprint">./heartbeat -e
</pre><p>As soon as Heartbeat starts to run, it will check the list of URLs you have configured, send back the information to the Elastic Stack, and pre-populate Kibana dashboards.
</p><h2>Visualizing Uptime Data in Kibana</h2><p>When you open Kibana, you will see Heartbeat information in the Discover tab when you select the Heartbeat index (<em>heartbeat-*</em> by default):
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt5f1a72995da64f21/5c304c38b7017c456eff096d/uptime1.png" data-sys-asset-uid="blt5f1a72995da64f21" alt="" style="display: block; margin: auto;">
</p><p>Among dashboards, you will find the “Heartbeat HTTP monitoring” dashboard that is populated with all of the information Heartbeat had sent:
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltc42315903e82183d/5c304c336e9992e16f529927/uptime2.png" data-sys-asset-uid="bltc42315903e82183d" alt="" style="display: block; margin: auto;">
</p><p>This is the default Heartbeat dashboard:
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blte098f9f798dac124/5c304c2fc05f480270a742b4/uptime3.jpg" data-sys-asset-uid="blte098f9f798dac124" alt="" style="display: block; margin: auto;">
</p><p>In the upper left corner you will see a table with a list of all Heartbeat-monitored endpoints, along with their response times. In the upper right, you will see the summary of the monitor status codes, and below it additional graphs which represent the percentage of monitors which are up or down, response time over time and number of checks over time.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltf87fdf066c90276f/5c304c2cc599e169662410e2/uptime4.png" data-sys-asset-uid="bltf87fdf066c90276f" alt="" style="display: block; margin: auto;">
</p><p>Heartbeat dashboards are interactive. With the default Heartbeat dashboard, you can easily detect if a specific endpoint is up or down, by clicking on the monitor down section (that is the red slice in the HTTP monitor status piechart located on the upper right corner). Clicking on it will apply a filter on the dashboard, which will display only the monitors which are down.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt83ee08b9cb1e606c/5c304c27c0508d076e1712cd/uptime5.png" data-sys-asset-uid="blt83ee08b9cb1e606c" alt="" style="display: block; margin: auto;">
</p><p>You can customize Heartbeat Kibana dashboards and visualizations in order to meet your needs. To get started with that, click the “Edit” button on the dashboard top right, click the gear on an individual visualization, and select “Edit Visualization”. You can also create new visualizations based on Heartbeat data, combine Heartbeat metrics with other log, metrics, and APM data sources, and add them to any operational dashboard you like.
</p><h2>Combining Heartbeat Data with Other Operational Data Sources</h2><p>Combing Heartbeat data with additional data sources such as Metricbeat, Filebeat, and APM can provide important information when triaging an outage. Heartbeat will notify you when a specific service is down, Metricbeat and APM can provide you with the potential suspects, it can significantly improve the MTTR and will focus everyone to look at the right place, instead of playing the “blame game” in a typical war room.
</p><p>Visit our <a href="/solutions">solution page</a> to learn more about our logging, metrics, and APM solutions.
</p><p>Here is an example for a Kibana dashboard which brings together metrics from Heartbeat (top two&nbsp;panels), and Metricbeat (bottom two&nbsp;panels).
</p><ul>
	<li>On the <u>left hand side</u> you can see that whenever Heartbeat detected that our endpoint is down, Metricbeat detects an increasing number of errors via the Nginx module.</li>
	<li>On the <u>right hand side</u> we can clearly see that whenever our HTTP ping time is increasing, Metricbeat detect high request rate in the NGINX server. </li>
</ul><p>Observing this coincidence, we can conclude that a massive spike in request rate is triggering Nginx errors, which, in turn, is causing Heartbeat checks to fail:
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blte57f75ff274d5d9c/5c304c23760e7f7a666d68c5/uptime6.jpg" data-sys-asset-uid="blte57f75ff274d5d9c" alt="" style="display: block; margin: auto;">
</p><h2>Alerting and Anomaly Detection</h2><p>You can use the <a href="/what-is/kibana-alerting">alerting capabilities</a> to get alerts and notifications on an outage or a performance degradation based on Heartbeat monitor data. You can also use the Elastic Stack <a href="/what-is/elasticsearch-machine-learning">machine learning</a> capabilities to detect any anomalies based on time-series analytics of Heartbeat data. More on that in my next Heartbeat blog.
</p><h2>Summary</h2><p>Monitoring can be a tough job. You need to identify, alert on, and resolve issues quickly. If today you are using multiple&nbsp;disparate tools to gain visibility across your applications and infrastructure, your task is likely even harder.
</p><p>Heartbeat adds effective uptime monitoring functionality on top of existing logs, metrics, and APM features in the Elastic Stack. Use it by itself, or combine it with other valuable sources of operational data in Elasticsearch&nbsp;—&nbsp;so you won't miss a beat!
</p><h2>Heartbeat Resources</h2><p>That’s it! Hope you found this overview useful. To get started, <a href="/downloads/beats/heartbeat">download Heartbeat</a> and read its&nbsp;<a href="/guide/en/beats/heartbeat/6.5/index.html">documentation</a> for more in-depth coverage of the functionality. One of the fastest ways to experience Heartbeat is to ship your uptime data to the <a href="/cloud/elasticsearch-service">Elasticsearch Service</a> on <a href="/cloud">Elastic Cloud</a> — the hosted Elasticsearch and Kibana offering from the creators of these projects.
</p>If you have questions, please engage with us on the Heartbeat <a href="https://discuss.elastic.co/c/beats/heartbeat">Discuss</a> forum, and if you find any issues or would like to file an enhancement request, please do so in <a href="https://github.com/elastic/beats/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3AHeartbeat+">Github</a>.

AUTHOR

Articles by Dov Hershkovitch

Elastic Uptime Monitoring 7.3.0 released

Elastic Uptime Monitoring 7.2.0 released

Elastic Uptime Monitoring solution released

Uptime Monitoring with Heartbeat and the Elastic Stack

Products & Solutions

Company

Resources

Solutions

Elastic (ELK) Stack

New

Featured topics

News

AUTHOR

Articles by Dov Hershkovitch

Elastic Uptime Monitoring 7.3.0 released

Elastic Uptime Monitoring 7.2.0 released

Elastic Uptime Monitoring solution released

Uptime Monitoring with Heartbeat and the Elastic Stack