Clarify activation method when version unknown (#783)

* clarify activation method when version unknown * Update specs/agents/metadata.md Co-authored-by: Trent Mick <[email protected]> --------- Co-authored-by: Trent Mick <[email protected]>
elastic · Apr 13, 2023 · 6b807a5 · 6b807a5
1 parent 22161a7
commit 6b807a5
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/specs/agents/metadata.md b/specs/agents/metadata.md
@@ -139,7 +139,8 @@ Services running on AWS Lambda [require specific values](tracing-instrumentation
 #### Activation method
 
 Most of the APM Agents can be activated in several ways. Agents SHOULD collect information about the used activation method and send it in the `service.agent.activation_method` field within the metadata.
-This field should only be sent when APM server version is at least `8.7.1`, and MUST be ommited in `8.7.0` due to a bug in APM server.
+This field MUST be omitted in version `8.7.0` due to a bug in APM server (preventing properly capturing metrics).
+This field SHOULD be included when the APM server version is unknown or at least `8.7.1`.
 
 The intention of this field is to drive telemetry so there is a way to know which activation methods are commonly used. This field MUST produce data with very low cardinality, therefore agents SHOULD use one of the values defined below.