# Capture HTTPS Certificate Expiration Dates using Heartbeat

**URL:** <https://discuss.elastic.co/t/capture-https-certificate-expiration-dates-using-heartbeat/77865>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [March 8, 2017, 5:50pm UTC](https://discuss.elastic.co/t/capture-https-certificate-expiration-dates-using-heartbeat/77865 "2017-03-08T17:50:16Z")\
**Posts on this page:** 5\
**Page:** 1

<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:** [March 8, 2017, 5:50pm UTC](https://discuss.elastic.co/t/capture-https-certificate-expiration-dates-using-heartbeat/77865/1 "2017-03-08T17:50:16Z")

</div>

I had the opportunity to ask @tudor this question at ElasticOn17 -- this might be a feature request.

Q: For the heartbeat HTTP monitor type, is it possible for Heartbeat to capture the HTTPS certificate expiration date (or days left until expiration) of the URL as a metric?

I am curious as to if this is possible or not as I have a need to monitor SSL certificate expiration dates for hundreds of our individual company websites (all of them have their own certificate expiration dates) and there isn't a great solution for this most anywhere else. Maybe Heartbeat can do this?

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [March 11, 2017, 5:44am UTC](https://discuss.elastic.co/t/capture-https-certificate-expiration-dates-using-heartbeat/77865/2 "2017-03-11T05:44:43Z")

</div>

Sounds like a great feature to me. I've been using check\_http in nagios for this and it would be nice to move it to Beats. I think we should track this one in Github. Can you please open an issue for it?

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [March 13, 2017, 6:39am UTC](https://discuss.elastic.co/t/capture-https-certificate-expiration-dates-using-heartbeat/77865/3 "2017-03-13T06:39:36Z")

</div>

This is currently not supported by heartbeat. I created an [enhancement request](https://github.com/elastic/beats/issues/3741) for heartbeat to track some TLS connection data.

---

<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:** [March 13, 2017, 11:18am UTC](https://discuss.elastic.co/t/capture-https-certificate-expiration-dates-using-heartbeat/77865/4 "2017-03-13T11:18:36Z")

</div>

Thank you Steffen!

---

<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:** [April 10, 2017, 11:18am UTC](https://discuss.elastic.co/t/capture-https-certificate-expiration-dates-using-heartbeat/77865/5 "2017-04-10T11:18:53Z")

</div>

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