Using multiple proxies » History » Version 1
Luke Murphey, 03/19/2014 04:01 PM
| 1 | 1 | Luke Murphey | h1. Using multiple proxies |
|---|---|---|---|
| 2 | 1 | Luke Murphey | |
| 3 | 1 | Luke Murphey | Website Monitoring has the ability to use separate proxy servers for each input. This can be useful when you want to test the performance of the proxy server itself. To enable this configuration, you will need to edit the conf files directly on the file-system (changing the settings via the user interface it not yet supported). Below are instructions: |
| 4 | 1 | Luke Murphey | |
| 5 | 1 | Luke Murphey | h2. Step one: define proxies |
| 6 | 1 | Luke Murphey | |
| 7 | 1 | Luke Murphey | First, you will need to define your proxy servers in the website_monitoring.conf. Start by creating or editing the file in +_$SPLUNK_HOME/etc/apps/website_monitoring/local/website_monitoring.conf_+. Then, define a stanza for each proxy server. See the "spec file":https://github.com/LukeMurphey/splunk-website-monitoring/blob/master/src/README/website_monitoring.conf.spec for the fields that are supported. Below is an example: |
| 8 | 1 | Luke Murphey | |
| 9 | 1 | Luke Murphey | <pre> |
| 10 | 1 | Luke Murphey | [proxy_california] |
| 11 | 1 | Luke Murphey | proxy_server=ca.proxy.acme.com |
| 12 | 1 | Luke Murphey | proxy_port=8080 |
| 13 | 1 | Luke Murphey | proxy_type=http |
| 14 | 1 | Luke Murphey | |
| 15 | 1 | Luke Murphey | [proxy_illinois] |
| 16 | 1 | Luke Murphey | proxy_server=il.proxy.acme.com |
| 17 | 1 | Luke Murphey | proxy_port=8080 |
| 18 | 1 | Luke Murphey | proxy_type=http |
| 19 | 1 | Luke Murphey | </pre> |
| 20 | 1 | Luke Murphey | |
| 21 | 1 | Luke Murphey | h2. Step two: define inputs |
| 22 | 1 | Luke Murphey | |
| 23 | 1 | Luke Murphey | You will now need to make your inputs and define which proxy configuration the input will use. Start by creating or editing the file in +_$SPLUNK_HOME/etc/apps/website_monitoring/local/inputs.conf_+. You will do this by adding a field named "configuration" set to the value of the configuration you want the input to use. Below is an example: |
| 24 | 1 | Luke Murphey | |
| 25 | 1 | Luke Murphey | <pre> |
| 26 | 1 | Luke Murphey | [web_ping://ca_proxy] |
| 27 | 1 | Luke Murphey | interval = 15m |
| 28 | 1 | Luke Murphey | title = SomeWebsite |
| 29 | 1 | Luke Murphey | url = http://SomeWebsite.com |
| 30 | 1 | Luke Murphey | configuration=proxy_california |
| 31 | 1 | Luke Murphey | |
| 32 | 1 | Luke Murphey | [web_ping://no_proxy] |
| 33 | 1 | Luke Murphey | interval = 15m |
| 34 | 1 | Luke Murphey | title = SomeWebsite |
| 35 | 1 | Luke Murphey | url = http://SomeWebsite.net |
| 36 | 1 | Luke Murphey | configuration=proxy_illinois |
| 37 | 1 | Luke Murphey | </pre> |
| 38 | 1 | Luke Murphey | |
| 39 | 1 | Luke Murphey | |
| 40 | 1 | Luke Murphey | If you want, you can first make the inputs using the user interface, and then add the configuration information to the inputs afterwards. |
| 41 | 1 | Luke Murphey | |
| 42 | 1 | Luke Murphey | After you done editing the file, restart Splunk to make sure the changes get recognized. |
| 43 | 1 | Luke Murphey | |
| 44 | 1 | Luke Murphey | h2. Step three: verify configuration |
| 45 | 1 | Luke Murphey | |
| 46 | 1 | Luke Murphey | After you have restarted Splunk, verify |