Troubleshoot data collection

Attention:

Alpha features described in this document are provided by Splunk to you "as is" without any warranties, maintenance and support, or service-level commitments. Splunk makes this Alpha feature available at its sole discretion and may discontinue it at any time. These documents are not yet publicly available and we ask that you keep this information confidential.

Use of Alpha features is subject to the Splunk Pre-Release Agreement for Hosted Services. Use these links to navigate to topics within this private preview:

.

For diagnosing general issues with the OpenTelemetry collector, see Troubleshoot the Splunk OpenTelemetry Collector.

In order to diagnose and troubleshoot issues with Secure Application telemetry specifically, you can enable and activate the debug exporter in your collector's logs/secureapp pipeline. The debug exporter allows the collector to send telemetry directly to the console.

  1. Add the debug exporter in the exporters section if not already present.

    exporters:
   # ...
   # Other exporters
   # ...
   debug:
      # Available levels are "basic", "normal", and "detailed"
      verbosity: detailed

  2. Activate the debug exporter by adding it to logs/secureapp pipeline. For example:

    service:
  pipelines:
    ...
    logs/secureapp:
      receivers: [routing/logs]
      processors: [memory_limiter, batch]
      exporters: [debug, otlphttp/secureapp]

  3. After activating the debug exporter in logs/secureapp pipeline, restart the collector.

  4. Restart the Java application. Wait for a few minutes for the application initialization to complete and inspect the output in the console of the collector. Capture the output and send to support for further analysis if required.

  5. After you have inspected and captured the debug output, you can deactivate the debug exporter from the logs/secureapp pipeline and restart the collector.

For diagnosing issues with the Secure Application JVM agent, collect the agent logs and send them to Support. The logs are located in the /tmp folder if the container is non-writable; otherwise they're in the folder from which the Secure Application JVM agent was launched. For example: 

/tmp/secure-app-otel-extension/argentoDynamicService/ossAgentArgentoExtensionService_10-27-2025-15.45.19_7033.log
/tmp/secure-app-otel-extension/argentoDynamicService/argento-security-extension/instances/dummy--1_otel/logs/mt-agent-initial-10-27-2025-15.45.19_7033.log