From 4bf2d01b3a836cc6aeb33104a6d37e6b90c42e80 Mon Sep 17 00:00:00 2001 From: Matthieu MOREL Date: Tue, 24 Oct 2023 00:34:37 +0200 Subject: [PATCH] Complete documentation for peer service mapping After providing the possibility to override peer.service attribute by host, port and path. This add documentation. Signed-off-by: Matthieu MOREL Co-authored-by: Severin Neumann --- .../instrumentation/java/automatic/agent-config.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/content/en/docs/instrumentation/java/automatic/agent-config.md b/content/en/docs/instrumentation/java/automatic/agent-config.md index 848a6c8b15f0..00c68720e6fe 100644 --- a/content/en/docs/instrumentation/java/automatic/agent-config.md +++ b/content/en/docs/instrumentation/java/automatic/agent-config.md @@ -127,6 +127,18 @@ Then, requests to `1.2.3.4` will have a `peer.service` attribute of `cats-service` and requests to `dogs-abcdef123.serverlessapis.com` will have an attribute of `dogs-api`. +Since Java agent version `1.31.0`, it is possible to provide a port and a path +to define a `peer.service`. + +For example, if set to the following: + + 1.2.3.4:443=cats-service,dogs-abcdef123.serverlessapis.com:80/api=dogs-api + +Then, requests to `1.2.3.4` will have no override for `peer.service` attribute, +while `1.2.3.4:443` will have have `peer.service` of `cats-service` and requests +to `dogs-abcdef123.serverlessapis.com:80/api/v1` will have an attribute of +`dogs-api`. + {{% /config_option %}} ### DB statement sanitization