# Central Config of APM agents in Kibana

**URL:** <https://discuss.elastic.co/t/central-config-of-apm-agents-in-kibana/320530>\
**Category:** APM\
**Tags:** java, ui\
**Created:** [December 6, 2022, 7:00am UTC](https://discuss.elastic.co/t/central-config-of-apm-agents-in-kibana/320530 "2022-12-06T07:00:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tarund](https://avatars.discourse-cdn.com/v4/letter/t/977dab/32.png) [@tarund](https://discuss.elastic.co/u/tarund)\
**Post date:** [December 6, 2022, 7:00am UTC](https://discuss.elastic.co/t/central-config-of-apm-agents-in-kibana/320530/1 "2022-12-06T07:00:47Z")

</div>

Hi Team, I have multiple java agents running for several applications on different servers. Currently, the config is specified in properties file. I want to be able to update some of the dynamic configs from Kibana for specific service name agents. In Kibana APM App, I only see 2 properties "transaction max spans" & "transaction sample rate" for some agents, while for other agents I can see ~8 additional properties. Not getting the "server\_urls" property in any of them.

1. Can we update the "server\_urls" property from Kibana or remotely through some other way
2. How do I get to see all properties for all agents in Kibana ?

**Kibana version** : 7.15.2

**Elasticsearch version** : 7.15.2

**APM Server version** : 7.15.0

**APM Agent language and version** : Java 1.18.1

---

<div class="post-metadata">

**Author:** ![Jonas\_Kunz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonas_kunz/32/110740_2.png) [@Jonas\_Kunz](https://discuss.elastic.co/u/Jonas_Kunz)\
**Post date:** [December 8, 2022, 12:26pm UTC](https://discuss.elastic.co/t/central-config-of-apm-agents-in-kibana/320530/2 "2022-12-08T12:26:22Z")

</div>

Hi @tarund ,

The config-options you see in the Kibana UI are the only ones currently supported for central configuration. Which specific options would you like to see there for the Java agent?

Regarding the configuration of `server_urls`:  
This is kind of a chicken-egg problem: When the java agent starts, it needs to know the `server_urls` property, because this URL will be used for fetching the configuration updates.  
If we would allow the update of the `server_urls` property via the central config, the agent would loose this update after a restart and would be stuck with the initially configured `server_urls` property.

However, the `server_urls` property is dynamic, meaning that it can be changed at runtime, for example by updating `elasticapm.properties`. You could for example achieve what you desire by centrally managing the roleout of `elasticapm.properties` to your machines outside of elastic.

---

<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:** [December 29, 2022, 8:26am UTC](https://discuss.elastic.co/t/central-config-of-apm-agents-in-kibana/320530/3 "2022-12-29T08:26:53Z")

</div>

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