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
Description of the problem including expected versus actual behavior: A "invalid memory address or null pointer dereference" error seems to be triggered when an APM agent drops spans, e.g. due to a very high number of spans and a low TransactionMaxSpans value.
In my case, the APM agent was configured to use the default value of TransactionMaxSpans. After adding instrumentation
via Elastic.Apm.StackExchange.Redis, the agent had to drop spans, which triggered this error. Increasing TransactionMaxSpans temporarily fixes this error.
Steps to reproduce:
Setup an Elastic-Agent
Add the APM integration and enable API key authentication
Create a new API key for authentication
Send the following request to the APM server (replace <YOUR-API-KEY> and <APM-SERVER-HOST>):
Hi @SecTex , we are aware of this issue. The root cause of this issue is that .NET agent is flattening the duration fields, which is not expected by apm-server. The correct way to pass the duration field is to use nested objects.
The handling for this unexpected flattened duration field is missing in 8.9 and it is already fixed in 8.10. However, although apm-server will no longer panic, the flattened duration field is still ignored. It will require .NET agent to fix the root cause for the field to be parsed properly.
APM Server version (
apm-server version
): 8.9.2Description of the problem including expected versus actual behavior: A "invalid memory address or null pointer dereference" error seems to be triggered when an APM agent drops spans, e.g. due to a very high number of spans and a low
TransactionMaxSpans
value.In my case, the APM agent was configured to use the default value of
TransactionMaxSpans
. After adding instrumentationvia Elastic.Apm.StackExchange.Redis, the agent had to drop spans, which triggered this error. Increasing
TransactionMaxSpans
temporarily fixes this error.Steps to reproduce:
<YOUR-API-KEY>
and<APM-SERVER-HOST>
):dropped_spans_stats
array does not trigger this error, suggesting that this is the cause of the problemProvide logs (if relevant):
The text was updated successfully, but these errors were encountered: