From 2c5fe1768a4cdd203ea267cad8dcab624981aef3 Mon Sep 17 00:00:00 2001 From: David Chan Date: Thu, 11 Aug 2022 16:04:13 -0400 Subject: [PATCH] Adresss further comments --- spec/src/main/asciidoc/architecture.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec/src/main/asciidoc/architecture.adoc b/spec/src/main/asciidoc/architecture.adoc index eb98a485..c72af9e9 100644 --- a/spec/src/main/asciidoc/architecture.adoc +++ b/spec/src/main/asciidoc/architecture.adoc @@ -154,7 +154,7 @@ Global tags and tags registered with the metric are included in the output retur Global tags MUST NOT be added to the `MetricID` objects. Global tags must be included in list of tags when metrics are exported. -NOTE: In application servers with multiple applications deployed, values of the reserved tag `mp_app` distinguishing metrics +NOTE: In application servers with multiple applications deployed, values of the reserved tag `mp_app` distinguish metrics from different applications and must not be used for any other purpose. For details, see section <>. @@ -294,7 +294,7 @@ The value of the `mp_app` tag should be passed by the application server to the It should be possible to override this value by bundling the file `META-INF/microprofile-config.properties` within the application archive and setting a custom value for the property `mp.metrics.appName` inside it. -It is allowed for application servers to choose to not add the `mp_app`` tag at all. Implementations may differ in how they handle cases where +It is allowed for application servers to choose to not add the `mp_app` tag at all. Implementations may differ in how they handle cases where metrics are registered with the same name from two or more applications running in the same server. This behavior is not expected to be portable across vendors.