# APM Integartion show the zone 1 proxy IP even its down in Server URL

**URL:** <https://discuss.elastic.co/t/apm-integartion-show-the-zone-1-proxy-ip-even-its-down-in-server-url/372394>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [December 26, 2024, 7:16am UTC](https://discuss.elastic.co/t/apm-integartion-show-the-zone-1-proxy-ip-even-its-down-in-server-url/372394 "2024-12-26T07:16:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kishorkumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kishorkumar/32/132930_2.png) [@kishorkumar](https://discuss.elastic.co/u/kishorkumar)\
**Post date:** [December 26, 2024, 7:16am UTC](https://discuss.elastic.co/t/apm-integartion-show-the-zone-1-proxy-ip-even-its-down-in-server-url/372394/1 "2024-12-26T07:16:45Z")

</div>

Hello everyone

I have an ECE setup with 3 zones, and I’ve added proxies to each zone. Additionally, I’ve assigned a VIP (Virtual IP) for all Kibana instances and other services to ensure seamless access. This setup is designed to handle zone failures so that, if one zone goes down, i can access with that VIP IP without interruption.

However, when I integrate APM, the APM UI shows a secret token and a URL pointing to the proxy IP of Zone 1 instead of the VIP.

So, my question is: When providing the APM URL for applications, should I use the proxy IP of Zone 1 or the VIP? The concern is that if Zone 1 goes down, and i try to get the APM URL it still shows the proxy IP for that zone 1 that no longer accessible.

Please advise. and explain how it works?

#Elasticsearch#Kibana#APM  
#observability-apm #orchestration-ece-elastic-cloud-enterprise #stack-elasticsearch