Currently tested manually on Centos 7, but we will eventually add automated.The expected directory structure is: $root_url/ The files must be placed according to directory structure example given below. Modulepath outside of the Splunk module because each deploy will overwrite the You'll need to override the splunk::params::src_root parameter to point at a
Once the module is in place, there is just a little setup needed.įirst, you will need to place your downloaded splunk installers into the filesĭirectory, /splunk/files/. Have the correct entry in your Puppetfile. You can also use r10k or code-manager to deploy the module so ensure that you This will place the module into your primary module path if you do not utilize To begin using this module, use the Puppet Module Tool (PMT) from the command Uses the vendor-generated service file to manage the splunk service.
Splunk inputs.conf add application tag install#
Or apt to install these components if they're self-hosted. Installation media will need toīe aquired seperately, and the module configured to use it. Splunk Universal Forwarder installation media. Additionally, this module does not supply Splunk or Firewall rules will need to beĬonfigured separately in order to allow for correct operation of Splunk and the This module does not configure firewall rules. It provides types/providers to interact with the various This module provides a method to deploy Splunk Enterprise or Splunk Universalįorwarder with common configurations and ensure the services maintain a running Development - Guide for contributing to the module.Reference - An under-the-hood peek at what the module is doing and how.
Splunk inputs.conf add application tag upgrade#
Upgrade splunk/splunkforwarder packages.Usage - Configuration options and additional functionality.Setup - The basics of getting started with splunk.Module Description - What the module does and why it is useful.
0 kommentar(er)
