Splunk AppDynamics

Soap call Unmarshalling Error

CommunityUser
Splunk Employee
Splunk Employee

I am making soap calls for google adwords api and it works in local but it gives error in server. Appdynamics running my server. When i made soap call in server gives me this error:

Unmarshalling Error: unexpected element (uri:"urn:appdynamics", local:"singularityheader"). Expected elements are 

<{https://adwords.google.com/api/adwords/cm/v201806}ApiExceptionFault>,

<{https://adwords.google.com/api/adwords/cm/v201806}RequestHeader>,

<{https://adwords.google.com/api/adwords/cm/v201806}ResponseHeader>,

<{https://adwords.google.com/api/adwords/cm/v201806}get>,

<{https://adwords.google.com/api/adwords/cm/v201806}getResponse>,

<{https://adwords.google.com/api/adwords/cm/v201806}mutate>,

<{https://adwords.google.com/api/adwords/cm/v201806}mutateLabel>,

<{https://adwords.google.com/api/adwords/cm/v201806}mutateLabelResponse

>,<{https://adwords.google.com/api/adwords/cm/v201806}mutateResponse>,

<{https://adwords.google.com/api/adwords/cm/v201806}query>,

<{https://adwords.google.com/api/adwords/cm/v201806}queryResponse>

Thanks

Labels (1)
0 Karma
1 Solution

Abhimanyu_Arora
Path Finder

Hi Necdet,

The error is because appdynamics adds a special singularity header on all soap calls to make correlation between appdynamics monitored application. Since, in this case of google adward service we don't need to correlete, you can create a custom backend rule from the controller UI to turn off this singularity header for this particular call.

Let me know if you need any help in doing the same.

Here is a document for reference - https://docs.appdynamics.com/display/PRO45/Backend+Detection+Rules

Thanks

Abhimanyu

View solution in original post

Abhimanyu_Arora
Path Finder

Hi Necdet,

The error is because appdynamics adds a special singularity header on all soap calls to make correlation between appdynamics monitored application. Since, in this case of google adward service we don't need to correlete, you can create a custom backend rule from the controller UI to turn off this singularity header for this particular call.

Let me know if you need any help in doing the same.

Here is a document for reference - https://docs.appdynamics.com/display/PRO45/Backend+Detection+Rules

Thanks

Abhimanyu

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...