# Heartbeat send other fields in alert message

**URL:** <https://discuss.elastic.co/t/heartbeat-send-other-fields-in-alert-message/237492>\
**Category:** Synthetics\
**Created:** [June 17, 2020, 3:01pm UTC](https://discuss.elastic.co/t/heartbeat-send-other-fields-in-alert-message/237492 "2020-06-17T15:01:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![matthiasbaldi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matthiasbaldi/32/70546_2.png) [@matthiasbaldi](https://discuss.elastic.co/u/matthiasbaldi)\
**Post date:** [June 17, 2020, 3:01pm UTC](https://discuss.elastic.co/t/heartbeat-send-other-fields-in-alert-message/237492/1 "2020-06-17T15:01:41Z")

</div>

We created Alerts for Heartbeat Monitors on our Cloudinstance (7.7).  
Currently the alerts are working, but the content which is sent to the Slack channel is a bit weired.  
There are a lot of IDs like the following one:`Down monitor: auto-http-0X34F47F1C6APD8A0B`  
We have correct and accurate information in the alert message, but how is it possible to access this message to get i.e. the `url.domain` attribute or the one of the custom fields?

Thank you.

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [June 19, 2020, 12:36am UTC](https://discuss.elastic.co/t/heartbeat-send-other-fields-in-alert-message/237492/2 "2020-06-19T00:36:36Z")

</div>

That's a great point. We should have the default message include URLs. I've created an [issue](https://github.com/elastic/kibana/issues/69602) to track this.

However, you should be setting the `monitor.id` attribute, which if not specified is autogenerated, and is the source of the gibberish you see. That value is what uniquely identifies a heartbeat monitor. Any change to the configuration block for that monitor will cause confusion in the UI if that's not specified because we can't know if the change represents a new logical monitor or an alteration to an old one. See [our docs](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-heartbeat-options.html) for examples.

---

<div class="post-metadata">

**Author:** ![matthiasbaldi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matthiasbaldi/32/70546_2.png) [@matthiasbaldi](https://discuss.elastic.co/u/matthiasbaldi)\
**Post date:** [June 19, 2020, 8:19am UTC](https://discuss.elastic.co/t/heartbeat-send-other-fields-in-alert-message/237492/3 "2020-06-19T08:19:25Z")

</div>

Worked. Thank you.  
This property was not that clear for me 🙂  
But please also think about an edit button for the uptime alerts and maybe a templateing possibility for alerts.  
Would be nice to have a somthing for that 👍

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [June 24, 2020, 7:27pm UTC](https://discuss.elastic.co/t/heartbeat-send-other-fields-in-alert-message/237492/4 "2020-06-24T19:27:23Z")

</div>

Hey, we're working on the edit button, targeting later this calendar year. There's a lot of machinery needed to go from Kibana -\> heartbeat to get into place.

---

<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:** [July 22, 2020, 7:37pm UTC](https://discuss.elastic.co/t/heartbeat-send-other-fields-in-alert-message/237492/5 "2020-07-22T19:37:27Z")

</div>

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