Possible Errors

Errors

Updating to APM Connector 3.0.0 could cause you to face some type of errors and here we will explain how you can handle them.

Null values

When you define where your trace information is in your operation you need to specify from where to take it. This could bring some issues if you use DataWeave to resolve the value and that value is null. You will see the next error message in that case.

How to handle this error?
You can validate the value using a default value to avoid getting null. You can use the next DataWeave expression as an example

Logs and traces not correlating

If you are having the problem that your application does not show the relations with its logs could be due to they are not correlated correctly
That means your Log4j2 configuration properties MUST match with your configuration set in your APM Global Configuration in next fields:

• env
• Service
• Version

Those three fields must match in order to show correctly the connection between logs and traces.

Examples

• The next is an example of a fully configured APM Connector with distributed tracing. 

• A create span connector with no distributed tracing, next is the general tab 

Distributed tracing tab