Use An Alternative Index » History » Version 1
Luke Murphey, 10/13/2017 07:59 PM
1 | 1 | Luke Murphey | h1. Use An Alternative Index |
---|---|---|---|
2 | 1 | Luke Murphey | |
3 | 1 | Luke Murphey | Website Monitoring can be setup to use an alternative index such that the data isn't stored in the "main" index. |
4 | 1 | Luke Murphey | |
5 | 1 | Luke Murphey | Here is how you set that up. |
6 | 1 | Luke Murphey | |
7 | 1 | Luke Murphey | h2. Step 1: Create Your Index |
8 | 1 | Luke Murphey | |
9 | 1 | Luke Murphey | Create your index within Splunk. See http://docs.splunk.com/Documentation/Splunk/latest/Indexer/Setupmultipleindexes. |
10 | 1 | Luke Murphey | |
11 | 1 | Luke Murphey | Then, click the checkbox next to "More settings" on the modular input configuration page for the input you want to go to that index. You should see a dropdown under the "Index" area that will allow you to select the index. |
12 | 1 | Luke Murphey | |
13 | 1 | Luke Murphey | Save the input. The data will now go to that index. |
14 | 1 | Luke Murphey | |
15 | 1 | Luke Murphey | h2. Step 2: Send the Data to Your Custom Index |
16 | 1 | Luke Murphey | |
17 | 1 | Luke Murphey | Modify your Website Monitoring inputs such that they send the data to the index you just created. You can do this by clicking the checkbox next to "More settings" on the modular input configuration page for the input you want to go to that index. You should see a dropdown under the "Index" area that will allow you to select the index. |
18 | 1 | Luke Murphey | |
19 | 1 | Luke Murphey | Save the input. The data will now go to that index. |
20 | 1 | Luke Murphey | |
21 | 1 | Luke Murphey | h2. Step 3: Tell the Website Monitoring to Load the Data from Your Custom Index |
22 | 1 | Luke Murphey | |
23 | 1 | Luke Murphey | Finally, modify the macro named "website_monitoring_search_index" within the Website Monitoring app to define the index (or indexes) where the data will reside. For example, if your index was named "web_data", then the macro value would be "(index=web_data)". The resulting macro should look like this in the macros.conf (etc/apps/website_montoring/local/macros.conf): |
24 | 1 | Luke Murphey | |
25 | 1 | Luke Murphey | <pre> |
26 | 1 | Luke Murphey | [website_monitoring_search_index] |
27 | 1 | Luke Murphey | definition = (index=web_data) |
28 | 1 | Luke Murphey | </pre> |
29 | 1 | Luke Murphey | |
30 | 1 | Luke Murphey | Note that you will need Website Monitoring 2.6 or greater to use this macro. |
31 | 1 | Luke Murphey | |
32 | 1 | Luke Murphey | Alternatively, you can also just set the index to be in the list of default search indexes. If you do that, you don't have to modify the macro at all. |