I just started with an Elastic APM PoC.
We are using 10 out of the max 10 message attributes for SQS messages.
The java instrumentation adds some more to the list - which results in an exception.
software.amazon.awssdk.services.sqs.model.SqsException: Number of message attributes [11] exceeds the allowed maximum [10].
I've seen also error with 12 attributes (=2 added by Elastic).
While I can understand that this is done to support distributed monitoring, this is hardly ideal in our scenario.
How can we disable this behaviour? (or disable SQS instrumentation altogether)
The agent should under no circumstances produce application errors really ...
Our logs are also flooded with these warnings from the agent which seems to be related to the above:
WARN co.elastic.apm.agent.impl.transaction.TraceState - sample rate already set to 1.0, trying to set it to 1.0 through header will be ignored