Recommendations Using the APM Connector 3.0.0

We have a list of recommendations or good practices when you are using the APM Connector 3.0.0, we highly recommend following them.

• Target variable: We recommend always storing the result of a create and update operations in a new variable. Using the connector like that you will avoid problems of overwriting your payload. You can see the next screenshot as an example to define your variable.  You can name your variable in the way you wish but we recommend using a name clearly and easily identifiable

• Version property in Global config and Log4j2: When you define the version in your global configuration that means that you will add a tag “version” in all your traces. But what if you want to add a Log operation to succesfully correlate both traces and logs you need to match the properties of your tags in traces and log configuration, this includes adding a version property. You can follow the example in the Global config new property: “version” section, for further details please visit Global Elements and Log4j section.

• Injection of baggage items with DataWeave function: You can use a DataWeave expression to send a variable that resolves in an object of key/value pair. This will help you to get all your properties at once instead define one by one each of your propagated tags.

• Propagations of baggage items with DataWeave function: You can use a DataWeave expression to send a variable that resolves in an object of key/value pair. This will help you to send all your properties at once instead set one by one each of your propagated tags.