You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for opening the issue! I agree, this would be nice to have.
Right now the protocol between agents and server does not support sending arbitrary logs, which is why things are the way they are. We are looking into extending the protocol (elastic/apm-server#3723); if/when that happens, then I think it would make sense to come back and add full support for LogKV.
The APM agent ships with an adapter for opentracing. Opentracing supports a
Span.LogKV
operation that is similar to a multi-SetTag
.And indeed, that is how it being used in at least one project, thanos.
However, it appears that the APM agent is only using this mechanism for logging error messages:
apm-agent-go/module/apmot/log.go
Lines 85 to 88 in 2aef45b
It would be great if custom, non-standard key-value entries were stored by the agent.
The text was updated successfully, but these errors were encountered: