Splunk AppDynamics

Data Collectors

Maria_Garcia
Path Finder

We have several HTTP SOAP calls to remote services related to queues.

In order to capture the information related to those SOAP calls (message, response, destination...), data collectors have been configured to capture the following String parameters:

  • Monitor.init(String, String, String, String, String, String)

However it would be nice being able to filter those information:

1) Some parameters contains a lof of lines, so Data collector is not able to display all of them:

... Max length limit [2000] reached, not all data points were captured]

How to obtain the missing information please?

2) Some results contains too much information:

[<outputMessage>

    <ns0:NoBPMCaseResponse xmlns:ns0="http://www.db.com/DPS/NoBPMCase" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

        <result>

            <ns1:result xmlns:ns1="http://www.db.com/Output/ResponseResult">OK</ns1:result>

        </result>

        <responseData>

            <documentId>6082</documentId>

        </responseData>

    </ns0:NoBPMCaseResponse>

</outputMessage>]

Could it be possible execute to filter specific data? For example, being able to display only the documentId value.

Thanks a  lot in advance!

Labels (1)

CommunityUser
Splunk Employee
Splunk Employee

You need to configure the Data Collector to capture the fields you need.

In Specify the Data to Collect from this Method Invocation configure the fields that capture information

Use Collect Data From Method index 0
Use Getter Chain toString (). Split (<field to be captured>). [1] .substring (int / 0, int / 19)

In (int) give the total number of characters that are to be captured, in the example above, 20 characters will be capturedimage.png

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...