# Autodiscover with synthetics

**URL:** <https://discuss.elastic.co/t/autodiscover-with-synthetics/387229>\
**Category:** Synthetics\
**Tags:** docker\
**Created:** [June 23, 2026, 3:40pm UTC](https://discuss.elastic.co/t/autodiscover-with-synthetics/387229 "2026-06-23T15:40:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cristian\_Pereyra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cristian_pereyra/32/126779_2.png) [@Cristian\_Pereyra](https://discuss.elastic.co/u/Cristian_Pereyra)\
**Post date:** [June 23, 2026, 3:40pm UTC](https://discuss.elastic.co/t/autodiscover-with-synthetics/387229/1 "2026-06-23T15:40:56Z")

</div>

Hello everyone.

The topic that brings us here is Heartbeat autodiscover. We have many deployments that are going to be modified and we need to automate the detection and creation of monitors.

The problem that is added to this is that Uptime, starting from version 8.15.0, is deprecated and the documentation recommends moving to Synthetics.

> **[Get started with Uptime | Elastic Docs](https://www.elastic.co/docs/solutions/observability/uptime/get-started)**
>
> Heartbeat is a lightweight daemon that you install on a remote server to periodically check the status of your services and determine if they are available...

We are looking for is:

1. To be able to do the same Heartbeat autodiscover but with Synthetics.
2. Heartbeat is still working in version 9.4.0 [Get started with Uptime | Elastic Docs](https://www.elastic.co/docs/solutions/observability/uptime/get-started#uptime-set-up-docker) — is it possible to use Heartbeat and see the monitors in the Synthetics section from that version?
3. We saw that there is an autodiscover using standalone agents by enabling the corresponding integration; however, the Synthetics integration is not available in the list:  
[Kubernetes autodiscovery with Elastic Agent | Elastic Docs](https://www.elastic.co/docs/reference/fleet/elastic-agent-kubernetes-autodiscovery)  
[Conditions based autodiscover | Elastic Docs](https://www.elastic.co/docs/reference/fleet/conditions-based-autodiscover)  
[Elastic integrations | Elastic integrations](https://www.elastic.co/docs/reference/integrations)

which path do you recommend we follow?

Regards.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [June 24, 2026, 1:38am UTC](https://discuss.elastic.co/t/autodiscover-with-synthetics/387229/2 "2026-06-24T01:38:05Z")

</div>

Closed duplicate of...

> [@Autodiscovery Strategy for Transitioning from Heartbeat to Synthetics](https://discuss.elastic.co/t/autodiscovery-strategy-for-transitioning-from-heartbeat-to-synthetics/387228):
>
> Hello everyone. The topic that brings us here is Heartbeat autodiscover. We have many deployments that are going to be modified and we need to automate the detection and creation of monitors. The problem that is added to this is that Uptime, starting from version 8.15.0, is deprecated and the documentation recommends moving to Synthetics. We are looking for is: To be able to do the same Heartbeat autodiscover but with Synthetics. Heartbeat is still working in version 9.4.0 [Get started wit…](https://www.elastic.co/docs/solutions/observability/uptime/get-started#uptime-set-up-docker)

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [June 24, 2026, 1:38am UTC](https://discuss.elastic.co/t/autodiscover-with-synthetics/387229/3 "2026-06-24T01:38:13Z")

</div>