# URL monitoring in Kibana

**URL:** https://discuss.elastic.co/t/url-monitoring-in-kibana/179314
**Category:** Beats
**Tags:** heartbeat
**Created:** [May 2, 2019, 8:58am UTC](https://discuss.elastic.co/t/url-monitoring-in-kibana/179314 "2019-05-02T08:58:16Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![ksunil](https://avatars.discourse-cdn.com/v4/letter/k/439d5e/32.png) [@ksunil](https://discuss.elastic.co/u/ksunil)
#### Post date: [May 2, 2019, 8:58am UTC](https://discuss.elastic.co/t/url-monitoring-in-kibana/179314/1 "2019-05-02T08:58:16Z")

</div>

Hi,

I got a requirement to monitor URL for example [http://testabc.com:8080/dcf](http://testabc.com:8080/dcf) .  
In general the url requires username and password to go through.  
But is there any way to get status code=200 without passing username and password in heartbeat.yml for this URL

---

<div class="post-metadata">

### Author: ![ksunil](https://avatars.discourse-cdn.com/v4/letter/k/439d5e/32.png) [@ksunil](https://discuss.elastic.co/u/ksunil)
#### Post date: [May 13, 2019, 3:15am UTC](https://discuss.elastic.co/t/url-monitoring-in-kibana/179314/2 "2019-05-13T03:15:19Z")

</div>

Hi,

Can i know any update

---

<div class="post-metadata">

### Author: ![joedissmeyer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joedissmeyer/32/26163_2.png) [@joedissmeyer](https://discuss.elastic.co/u/joedissmeyer)
#### Post date: [May 15, 2019, 3:34pm UTC](https://discuss.elastic.co/t/url-monitoring-in-kibana/179314/3 "2019-05-15T15:34:05Z")

</div>

@ksunil, I understand not wanting to include the user and pass information. We have the same requirements for several URLs that we monitor with Heartbeat.

You will want to look at configuring the `check.response.status` option for the URL you need to monitor. This will tell Heartbeat what the expected HTTP status code returned by the endpoint should be when things are "good".

For example, a URL that is secured with a username and password will respond with an HTTP status code of `401 Unauthorized` if correct credentials are not provided. 401 would be an expected response for your use case. Thus, using Heartbeat you can define an HTTP monitor that looks something like this:

```auto
- type: http
  schedule: '@every 30s'
  urls: ["http://testabc.com:8080/dcf"]
  check.response.status: 401

```

Using this example, if the URL returns the HTTP status code of `401` then Heartbeat will output the `monitor.status` of "UP" and all will be well with the world 🙂

Definitely check the official docs for detailed info on this configuration option.  
[https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-heartbeat-options.html](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-heartbeat-options.html)

- Joey D

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 12, 2019, 3:34pm UTC](https://discuss.elastic.co/t/url-monitoring-in-kibana/179314/4 "2019-06-12T15:34:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
