Getting Data In

Multiple wildcards for file path in inputs.conf

budimaos
Engager

I need to monitor a file under multiple similar paths, the full path can be dynamic so putting absolute path is not an option.

Actual path example: E:\OpenPages\profiles\OpenPagesNode1\logs\OpenPagesNodeServer2Server3\http_error.log

So I have the following monitor stanza and it doesn't pick up the files. Nothing useful in _internal log which indicate any problem.

[monitor://E:\OpenPages\profiles\OpenPagesNode*\logs\OpenPagesNodeServer*\http_error.log]

I suspect it's due to multiple wildcards on the path, since other file with similar stanza picked up just fine, as below,

[monitor://E:\OpenPages\profiles\OpenPagesNode*\logs\ffdc\(nodeagent|OpenPagesNode)*.log]

I can't really play around with it at the moment, but I'm pretty sure it'll work if I use the following monitor stanza instead,

[monitor://E:\OpenPages\profiles\...\http_error.log]

But I want to avoid it if possible since it will force the forwarder to traverse through all irrelevant subdirectories.

Any good suggestion?

Tags (1)
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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...