App Agent Node Properties (A)

This property is useful in environments where multiple backend instances share the same name but are distinguished by specific configuration parameters. For example, you have two backend services named PaymentService, but one is configured with error policy and the other one is configured with a different retry policy. By default, Java Agent will consolidate these into a single PaymentService node. To distinguish these backends, add the add-match-config-to-backend-identity property to your node configuration and set it to True.

When enabled, the Java Agent evaluates the matched configurations. If the configurations differ, the agent reports them as distinct backends in the Controller UI, allowing it for independent monitoring and alerting for each specific configuration profile.

This property resolves issues where log correlation metadata is missing or incomplete in applications that utilize multiple classloaders. By default, the Java Agent only instruments the classloader that initiates the transaction. If the logging framework is loaded by a different classloader, the agent may fail to inject correlation IDs. To enable cross-classloader log metadata injection, add the allow-delayed-log-metadata-enrichment property to your node configuration and set it to True.

When enabled, the Java Agent extends its metadata injection logic to identify and instrument the appropriate classloaders. This ensures that log correlation IDs are correctly propagated and visible in your logging backend, regardless of which classloader initialized the transaction.