Splunk AppDynamics

Split a service endpoint with POJO return value

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I am creating a custom POJO type service endpoint and want to split it using the return vlaue of the method. 

I could use the "POJO Object Instance to name transcations", unfortunately the method that I want to use takes an argument.

Please let me know how I can do this.

Thanks,

Muthu

Labels (1)
0 Karma
1 Solution

Vijay_Kumar_Ant
Explorer

Hi Muthu,

You cannot do that. It does not make sense to split a SEP with POJO return value. SEPs are inbound calls which invokes a method(POJO).  For an incoming request when you want to split the SEP you can split  with a method paramter and not when after the method is invoked and you have a response/return value. This is not a Data Collector where you are trying to collect data from a method invocation in which case you can collect either from method paramter or from return value.  

Hope this helps.

Thanks,

VJ

View solution in original post

Atyuha_Pal
Contributor

Hi Muthu,

Could you please check with the transaction splitting option available under custom service end point. Please refer to the below doc and attached screenshots.

https://docs.appdynamics.com/display/PRO42/Service+Endpoints#ServiceEndpoints-config_sep

Thanks,

Atyuha

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

The transaction splitting option available under custom service end point "Transaction Splitting" dose not show any options to split using the return value of the method.

I am looking for a splitting option which would split the service endpoint using the return vlaue of the method.

Can you please let me know if there is a way to achieve this?

Thanks,

Muthu 

0 Karma

Vijay_Kumar_Ant
Explorer

Hi Muthu,

You cannot do that. It does not make sense to split a SEP with POJO return value. SEPs are inbound calls which invokes a method(POJO).  For an incoming request when you want to split the SEP you can split  with a method paramter and not when after the method is invoked and you have a response/return value. This is not a Data Collector where you are trying to collect data from a method invocation in which case you can collect either from method paramter or from return value.  

Hope this helps.

Thanks,

VJ

CommunityUser
Splunk Employee
Splunk Employee

Thanks make sense

0 Karma
Get Updates on the Splunk Community!

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...

Leverage Cisco Talos Threat Intelligence Across Splunk Security Products

Leverage Cisco Talos Threat Intelligence Across Splunk Security Products   Security Edition   Have you ...

What’s New in Splunk Enterprise 9.4: Tools for Digital Resilience

What’s New in Splunk Enterprise 9.4: Tools for Digital Resilience Tune in to What’s New in Splunk Enterprise ...