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

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...