Why Agent Configuration always not aplied


how to apply the config ? my agent is alive

Hi, I'm not entirely sure what you are asking and what you are expecting. The Java agent documentation may help. Please could you be more detailed about what you are expecting and what you have tried so far. Thanks


i creat a config set recording=false,but the agent still report to server.it has a tip : not yet applied by any agent. how to make the config recording=false work ?

This should work. I just tested on an example server and Java agent, it propagated recording false, with the agent logging

2022-01-11 12:08:23,653 [elastic-apm-remote-config-poller] INFO  co.elastic.apm.agent.impl.ElasticApmTracer - Tracer switched to PAUSED state
2022-01-11 12:08:23,662 [elastic-apm-remote-config-poller] INFO  co.elastic.apm.agent.configuration.ApmServerConfigurationSource - Received new configuration from APM Server: {recording=false}

To look at this further I'll need all the details you can give. Server version, agent version, what type of Java application ...

the way to set up the Elastic APM Java Agent is [Programmatic API setup to self-attach],
server version=7.16.1,
agent version=1.28.4,
here is all the agent prints log, cant see the [elastic-apm-remote-config-poller] log
all server configs are default except the recording=false

2022-01-12 08:34:56,259 [Attach Listener] INFO  co.elastic.apm.agent.util.JmxUtils - Found JVM-specific OperatingSystemMXBean interface: com.sun.management.OperatingSystemMXBean
2022-01-12 08:34:56,409 [Attach Listener] INFO  co.elastic.apm.agent.configuration.StartupInfo - Starting Elastic APM 1.28.4 as dev_market on Java 11.0.13 Runtime version: 11.0.13+10-LTS-370 VM version: 11.0.13+10-LTS-370 (Oracle Corporation) Linux 3.10.0-693.el7.x86_64
2022-01-12 08:34:56,409 [Attach Listener] INFO  co.elastic.apm.agent.configuration.StartupInfo - service_name: 'dev_market' (source: Attachment configuration)
2022-01-12 08:34:56,410 [Attach Listener] INFO  co.elastic.apm.agent.configuration.StartupInfo - environment: 'dev' (source: Attachment configuration)
2022-01-12 08:34:56,410 [Attach Listener] INFO  co.elastic.apm.agent.configuration.StartupInfo - server_url: 'http://172.1.1.16:8200' (source: Attachment configuration)
2022-01-12 08:34:56,410 [Attach Listener] INFO  co.elastic.apm.agent.configuration.StartupInfo - metrics_interval: '10s' (source: Attachment configuration)
2022-01-12 08:34:56,410 [Attach Listener] INFO  co.elastic.apm.agent.configuration.StartupInfo - application_packages: 'com.algotrade.linkx.market' (source: Attachment configuration)
2022-01-12 08:35:12,378 [Attach Listener] INFO  co.elastic.apm.agent.impl.ElasticApmTracer - Tracer switched to RUNNING state
2022-01-12 08:35:12,831 [elastic-apm-server-healthcheck] INFO  co.elastic.apm.agent.report.ApmServerHealthChecker - Elastic APM server is available: {  "build_date": "2021-12-11T00:47:02Z",  "build_sha": "788b59e74cb7c08241fcc51b1c4eb93af5f774e2",  "publish_ready": true,  "version": "7.16.1"}
2022-01-12 08:35:20,613 [main] INFO  co.elastic.apm.agent.micrometer.MicrometerMetricsReporter - Registering Micrometer MeterRegistry: io.micrometer.core.instrument.simple.SimpleMeterRegistry@5807efad

How is APM Server running? Is it running as an Elastic Agent / Fleet integration? Or is it running standalone (legacy)?

run as an Elastic Agent

OK, thanks for confirming. There is a bug in the UI, related to running APM as an Elastic Agent integration: [APM] agent config applied indicator does not work with Fleet integration · Issue #123109 · elastic/kibana · GitHub. Sorry for the inconvenience.

Hey axw,
If APM server running standalone(legacy) (on docker). I have this kind of issue. But when I looked at discovery, show only metrics, not on APM service.