I have installed (several times) the Splunk App for Unix (*nix) Version 6.0.1. I have changed the default index in the settings to use the index=main by editing the related search Macro. I have configured the SUFs 'downstream' to send data to the main index and I can see all the data arriving in the index as expected. Note this is installed on a Splunk dedicated single instance running version 8.1.3 (Enterprise On-Premises)
In the settings section of the App, I can see the correct index is specified (main) and clicking on the various Preview button options returns valid data. See below for examples:
Index Specification, and verify "Preview " selections:
CPU data preview:
DF Data Preview:
Suffice it to say that all the other Preview buttons also return valid data. This would imply that the data is correctly configured and the applicaiton should be able to consume it.
However, when I try and look at the dashboards of the app, they all remain free of any data, as can be seen from the screen captures below:
I am kinda out of ideas. Anyone got anything?
Cheers
Chris
The add-on shouldn't be used graphically on the Windows instance. The add-on's main purpose is to extract fields so that your App shows data in the dashboards. So ideally you would have the following set up:
Linux Boxes: Add-on for Unix
Windows Box: App for Unix, Add-on for Unix
Data will send from the Linux boxes (with inputs turned on which you have) to the Windows box. You may need to restart the Windows box, but it *should* populate the dashboards if the addon is present on the Windows box.
It is essentially the process that malmoore lays out in this post:
Let me know if you get any further!
Chris,
Is the addon installed on the instance as well and not just on the forwarder(s)? This seems similar to the linked Community post below yet not exactly.
Hope that helped!
I have the Splunk TA for Linux deployed to my two test servers and their conmfiguration is what is sending the data through to the main index:
I had to manually change the permissions on the .sh and .py files due to my deployment server being a Windows box, but they are both sending all the expected telemetry from the SUF and TA to the main index.
...I had assumed, as the indexer was Windows, that it would not need the TA, but I will try that next - thanks!
Looks like the indexer might have to be a Linux box too - annoying!
The add-on shouldn't be used graphically on the Windows instance. The add-on's main purpose is to extract fields so that your App shows data in the dashboards. So ideally you would have the following set up:
Linux Boxes: Add-on for Unix
Windows Box: App for Unix, Add-on for Unix
Data will send from the Linux boxes (with inputs turned on which you have) to the Windows box. You may need to restart the Windows box, but it *should* populate the dashboards if the addon is present on the Windows box.
It is essentially the process that malmoore lays out in this post:
Let me know if you get any further!
Victory: you are a STAR
See the app troubleshooting guide at https://docs.splunk.com/Documentation/UnixApp/6.0.0/User/TroubleshoottheSplunkAppforUnixandLinux
If that doesn't help then open a Splunk support request.
Alas, I am but a humble tinkerer and dol not have paid support options! 😞