Getting Data In

Are there adverse affects to having monitors for files that do not exist?

brent_weaver
Builder

I have two platforms to monitor. I want to create one application that I can apply to all hosts that come on board. I know that Spunk will not scream anymore with 6.2.x, but are there adverse affects? Will it create errors in the Spunk log files?

Tags (2)
0 Karma

martin_mueller
SplunkTrust
SplunkTrust

You won't see any errors, not finding a file is expected behaviour. You also won't see any performance issues if you keep the number of monitors reasonable. You might see unexpected indexing if one platform one day happens to create a file in a path that exists in the other platform.

For clarity, maintenance, extendability, fewer cross-platform dependencies, etc. I'd advise to create two tailored apps nonetheless.

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...