# Network Maps

**URL:** <https://discuss.elastic.co/t/network-maps/358515>\
**Category:** Kibana\
**Tags:** vega, visualisation\
**Created:** [April 30, 2024, 7:34pm UTC](https://discuss.elastic.co/t/network-maps/358515 "2024-04-30T19:34:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [April 30, 2024, 7:34pm UTC](https://discuss.elastic.co/t/network-maps/358515/1 "2024-04-30T19:34:18Z")

</div>

Hello,

I wonder if anyone has figured out how to create a network topology map in Elastic?

I have tried Graphs but that doesn't seem viable.

I am considering creating a custom visualization using vega but wanted to see if that even is possible.

I want to something like this, where I would add Heartbeat data :  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/7/27296867c3d59af3a624832a400629ca7d21ea26.jpeg)

---

<div class="post-metadata">

**Author:** ![Marco\_Liberati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marco_liberati/32/82953_2.png) [@Marco\_Liberati](https://discuss.elastic.co/u/Marco_Liberati)\
**Post date:** [May 2, 2024, 7:31am UTC](https://discuss.elastic.co/t/network-maps/358515/2 "2024-05-02T07:31:03Z")

</div>

Hi @erikg

sure, network visualization can be achived with Vega: [Force Directed Layout Example | Vega](https://vega.github.io/vega/examples/force-directed-layout/)

The tricky part would be to get the right data from Elasticsearch to build it, as depending on the use case, can require multiple requests for a single visualization.

---

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [May 3, 2024, 3:09pm UTC](https://discuss.elastic.co/t/network-maps/358515/3 "2024-05-03T15:09:39Z")

</div>

Thanks, I want to use Heartbeat/Synthetics data, be able to visualize the up and down status and each node would be a host/monitor.

I think the tricky part would be showing the relationships. The relationships that would be either manually added or additional data source would be used to define the relationships.