# Tcp/tcp.go:230 dial failed with: dial tcp localhost:8095: i/o timeout

**URL:** https://discuss.elastic.co/t/tcp-tcp-go-230-dial-failed-with-dial-tcp-localhost-i-o-timeout/302261
**Category:** Elasticsearch
**Tags:** elastic-agent
**Created:** [April 12, 2022, 5:23pm UTC](https://discuss.elastic.co/t/tcp-tcp-go-230-dial-failed-with-dial-tcp-localhost-i-o-timeout/302261 "2022-04-12T17:23:04Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![BKS](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@BKS](https://discuss.elastic.co/u/BKS)
#### Post date: [April 12, 2022, 5:23pm UTC](https://discuss.elastic.co/t/tcp-tcp-go-230-dial-failed-with-dial-tcp-localhost-i-o-timeout/302261/1 "2022-04-12T17:23:04Z")

</div>

Hi,

I have configured heartbeat service to monitor the micro services to get the status of up/down.

In Kibana heartbeat dashboard, status is showing as down, but in actually the service is running over the mentioned port the in heartbeat yml file.

I can see below error from heartbeat log.

"error": {  
"type": "io",  
"message": "dial tcp localhost:8080: i/o timeout"  
}

2022-04-12T19:14:27.598+0200 DEBUG [tcp] tcp/tcp.go:230 dial failed with: dial tcp localhost:8080: i/o timeout.

Heartbeat is installed in host1 and micro service is running in localhost.

---

<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: [May 10, 2022, 5:23pm UTC](https://discuss.elastic.co/t/tcp-tcp-go-230-dial-failed-with-dial-tcp-localhost-i-o-timeout/302261/2 "2022-05-10T17:23:07Z")

</div>

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