# Heartbeat on elastic agent

**URL:** https://discuss.elastic.co/t/heartbeat-on-elastic-agent/309570
**Category:** Elastic Agent
**Tags:** elastic-agent
**Created:** [July 13, 2022, 6:05pm UTC](https://discuss.elastic.co/t/heartbeat-on-elastic-agent/309570 "2022-07-13T18:05:37Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![lineconnect](https://avatars.discourse-cdn.com/v4/letter/l/ecae2f/32.png) [@lineconnect](https://discuss.elastic.co/u/lineconnect)
#### Post date: [July 13, 2022, 6:05pm UTC](https://discuss.elastic.co/t/heartbeat-on-elastic-agent/309570/1 "2022-07-13T18:05:37Z")

</div>

Hi there,

we're using EFK in k8s and beats for a while now and want to migrate our beats to elastic agent.  
I've setup the agents to use the fleet server and i'm also able to configure the inputs trough Kibana.  
But i'm stuck with migrating heartbeat to elastic agent. The only integration i can find is 'Synthetics' but there is no option for kubernetes auto discovery and to use hints in annotations.

Within the elastic-agent image all binaries are there, also for heartbeat but i can't find a way to configure heartbeat like with the heartbeat.yml.

I'm i overlooking something or do i haven't seen the option to use k8s autodicovery and hint based uptime monitors?  
Or is it simply not possible?

BR,  
lineconnect

---

<div class="post-metadata">

### Author: ![MichelLaterman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michellaterman/32/110221_2.png) [@MichelLaterman](https://discuss.elastic.co/u/MichelLaterman)
#### Post date: [July 18, 2022, 6:35pm UTC](https://discuss.elastic.co/t/heartbeat-on-elastic-agent/309570/2 "2022-07-18T18:35:32Z")

</div>

I believe that heartbeat currently runs under the synthetics integration (currenly in beta) under the agent [Elastic Synthetics | Elastic Documentation](https://docs.elastic.co/integrations/synthetics)

---

<div class="post-metadata">

### Author: ![lineconnect](https://avatars.discourse-cdn.com/v4/letter/l/ecae2f/32.png) [@lineconnect](https://discuss.elastic.co/u/lineconnect)
#### Post date: [July 18, 2022, 6:52pm UTC](https://discuss.elastic.co/t/heartbeat-on-elastic-agent/309570/3 "2022-07-18T18:52:42Z")

</div>

Yes but there is no autodiscover functionality(as far as i've seen). Or is there anything?  
We've 200+ services which needs to be in that. It would be a mess to have a single synthetic integration for each of them

---

<div class="post-metadata">

### Author: ![MichelLaterman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michellaterman/32/110221_2.png) [@MichelLaterman](https://discuss.elastic.co/u/MichelLaterman)
#### Post date: [July 19, 2022, 12:57am UTC](https://discuss.elastic.co/t/heartbeat-on-elastic-agent/309570/4 "2022-07-19T00:57:52Z")

</div>

Unfortunately you are correct, however hints based autodiscovery is already on our backlog: [Add support for hints' based autodiscovery in kubernetes provider · Issue #662 · elastic/elastic-agent · GitHub](https://github.com/elastic/elastic-agent/issues/662)

---

<div class="post-metadata">

### Author: ![lineconnect](https://avatars.discourse-cdn.com/v4/letter/l/ecae2f/32.png) [@lineconnect](https://discuss.elastic.co/u/lineconnect)
#### Post date: [July 19, 2022, 6:29am UTC](https://discuss.elastic.co/t/heartbeat-on-elastic-agent/309570/5 "2022-07-19T06:29:28Z")

</div>

Alright. At least I have not overlooked anything.

---

<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: [August 16, 2022, 6:30am UTC](https://discuss.elastic.co/t/heartbeat-on-elastic-agent/309570/6 "2022-08-16T06:30:06Z")

</div>

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