Splunk AppDynamics

Data collector Error

Gopi_Krishnan
Explorer

Hi,

I have created a data collector for a particular response to be captured. I want only a certain part of it to be captured and am using the split function. So the response is below

Success
{
"data": {
"customerId": "1128477",
"contactInformation": {
"email": "[email protected]",
"mobileCountryCode": "0091",
"mobileNumber": "1234567890"

I want to capture the customerId and the data collector I am using is

getData().toString().split("customerId":).[1].split(,).[0] 

and this gives me output 

[CANNOT EVALUATE: No target specified]

Am I missing something or doing something wrong? The initial part getData().toString() gives me all the response details but when I try to split it to capture customerId then it gives me the above error. Please help

Regards,

Gopikrishnan

Labels (1)
Tags (1)
0 Karma
1 Solution

Morelz
Motivator

Hi there

There are special characters you have to escape e.g commas

A working getter chain would be like

This will also remove the " and just return the number

getData().toString().split(customerId": ).[1].split(").[0]

To change your one to a working one it would like below

getData().toString().split("customerId":).[1].split(\,).[0]

Ciao

View solution in original post

0 Karma

Morelz
Motivator

Hi there

There are special characters you have to escape e.g commas

A working getter chain would be like

This will also remove the " and just return the number

getData().toString().split(customerId": ).[1].split(").[0]

To change your one to a working one it would like below

getData().toString().split("customerId":).[1].split(\,).[0]

Ciao

0 Karma

Gopi_Krishnan
Explorer

Thanks for this.

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...