I'm hoping to get some help with the NMON app, because I'm having trouble getting anything to show up in the nmon_data sourcetype. In our environment, we're in "cold" mode. Our linux team has a central repository for nmon files. They get copied from the servers to the central repository once a day.
For now, I'm just trying to get his working in our Test splunk env. For that environment, we have a Search Head and an Indexer. The Search Head has access to the central repository, so it is the forwarder in this case as well.
I have the nmon app deployed to the search head and created a local inputs.conf to monitor our share. I also disabled the default nmon monitor that pointed $SPLUNK_HOME/var/run/nmon....
I created the index manually on our indexer and also installed the PA-nmon app as well (although not sure if necessary since parsing should take place on the search head). I disabled all of the inputs in that app.
Once I restart Splunk, I do see that the nmon files are processed (nmon_processing sourcetype), but no perfdata ever gets indexed. I verified that Splunk is watching the csv_repository directory. But I don't think anything ever shows up in that directory.
I've tested the script manually by cat'ing a file directly to the script (as outlined in the nmon wiki). When running the python script, there was an error about "Encountered an Unexpected error while trying to analyse the ending period of this Nmon". So I updated nmon2csv.sh to launch the perl script instead. When testing the perl script directly, the output looks good (I think). But no nmon.csv files are created there either, only the config data is created.
I'm not sure what I'm missing. I follow the script as best I can, but not well enough to determine in what scenario the nmon.csv file doesn't get created.
Any help would be appreciated. I didn't want to clutter this initial post with all of the config files / script outputs / splunk logs / etc. But I can provide whatever might help resolve the issue.
... View more