Installation

Troubleshooting custom modular input issues after Splunk update.

eden60
Engager

Hello Splunk Community,

I'm encountering an issue with a custom app I've developed for Splunk. The app is designed to collect and analyze data from various sources, and it has been working perfectly until recently. However, after a recent update to Splunk, I've noticed that some of my custom data inputs are not functioning as expected.

Specifically, I've configured data inputs using the modular input framework, and these inputs were collecting data without any problems. Now, I'm seeing errors in the logs related to these inputs, and data ingestion has become inconsistent.

Has anyone else experienced similar issues with modular inputs after a Splunk update? Are there any known compatibility issues or changes in the latest Splunk version that might affect custom data inputs? I'd appreciate any insights or suggestions on how to troubleshoot and resolve this problem.

Thanks in advance!

Labels (3)
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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...