Go to "Whitelisting / Import Base Lookups Data" and successively import and save each base lookup exported at the previous step to the matching whitelisting lookup. Go back to the App, and go to "Whitelisting / Export Base Lookups" and successively hit "Export" each base lookup. Go to "Whitelisting / Generate Base Lookups" and generate a base lookup by hitting "Run" for each report from 03 to 05. Then, configure each of the other lookups by following the steps below: Reload nf for the fresh lookups to be taken into account by using: http(s)://yourSplunkSearchHead/en-US/debug/refresh?entity=admin/transforms-lookup Populate empty lookups for each whitelist lookup by going to "Whitelisting / Generate Base Lookups" and hitting "Run" for "Mad Props - 02 - Generate initial empty whitelist lookups". Populate the madprops_active_sourcetypes_lookup first by going to "Whitelisting / Generate Base Lookups" and hitting "Run" for "Mad Props - 01 - Generate initial lookup for active sourcetypes". The madprops_apps_whitelist_lookup lets you whitelist Apps from the searches. The madprops_parameters_whitelist_lookup lets you whitelist specific parameters within a particular sourcetype. The madprops_sourcetypes_whitelist_lookup lets you whitelist entire sourcetypes from the results. The madprops_active_sourcetypes_lookup maintains a list of active (last 24h) sourcetypes. To adjust configuration later on, use the "App Configuration" view.ģ - Four lookups are being used within this app. To integrate your Heavy Forwarder(s), see Notes at the bottom of this README. Configuration Stepsġ - Install the App on your Splunk Search Head(s).Ģ - Provide the App with the hostname(s) of your Indexer(s) by following the initial configuration of the App.įor a standalone Splunk platform, use "local" or "*"įor a single Indexer platform, use the hostname of the Indexer.įor a platform with multiple Indexers, use wildcards to match the hostnames of the Indexers. Prerequisitesĭeploy Lookup File Editor ( ) on your Splunk Search Head. To avoid messing the score, a set of lookups lets you whitelist either apps, sourcetypes, or parameters. However, occasions arise where configuring certain parameters is not relevant. With this knowledge, a configuration score is calculated for each sourcetype. The App checks the configuration of your Indexers by calling the configs/conf-props API endpoint, and by differentiating between configured parameters and those left unchanged. This best practice of configuring the magic six nf parameters is mentioned in Andrew Duca's. Additionally, Mad Props provides a handy sourcetype browser that facilitate configuration checking between mutually dependent attributes from nf and nf. Mad Props lets you quickly find out how are configured the magic six nf parameters on your Indexers by browsing configuration through API calls. Hence, configuring these parameters - sometimes referred to as the magic six - is said to enhance indexing performances. When configuring Splunk to onboard data, it is a best practice to configure the six following nf parameters: TIME_PREFIX, TIME_FORMAT, MAX_TIMESTAMP_LOOKAHEAD, SHOULD_LINEMERGE, LINE_BREAKER and TRUNCATE.īy doing so, Splunk will know how to process events and will avoid spending resources guessing it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |