Closed SylvainJuge closed 1 year ago
FWIW, this likely means that a fast first Lambda invocation will not send activation_method
in metadata, because it will have data to send on before the APM server version check request has time to respond.
That's a very good point, and it would also be problematic for all the features that depend on agent version.
Maybe it's better to optimistically assume that the APM Server version is not 8.7.0 and only disable sending activation_method
when the version info request returns. As the bug that leads to document rejection only affects internal metrics which are, by default, scheduled every 30s, there's a good chance that we know about the version of the server before sending the first metrics.
+1 to send this field when the server version is unknown, and only explicitly omit it when we know it's 8.7.0. Do you think it's worth re-modify the spec for this small but important implementation detail ?
yes
second take for specification: PR #783
Closing this issue as all impacted agents have been updated.
Description
Only send the
service.agent.activation_method
when APM server is AT LEAST `8.7.1 or unknown (assume it's not 8.7.0 by default).Specification changes: #780 #783
I found only the following agents are impacted as their code already reference this field: java, dotnet, nodejs and python
Agent Issues