Documentation: 3.3
|  Print Version Contents
This page last updated: 07/03/08 02:07pm

Field actions

Enable interactions between your indexed fields and other web resources via field_actions.conf. For example, enable a reverse lookup of an IP address. Edit field_actions.conf in $SPLUNK_HOME/etc/system/local/, or your own custom application directory in $SPLUNK_HOME/etc/apps/. For more information on configuration files in general, see how configuration files work.

NOTE: You must both restart your Splunk server and clear your browser's cache before any changes take place.

Configuration

Add a stanza to specify which host, uri and label to use for your custom field action. Once this is enabled, your label will be added to the drop down menu next to the field specified by the metaKeys attribute. Other attribute/value pairs are available for stanzas in field_actions.conf.

Show source is a type of field action. If the host or source fields are not present then Show source is not available from the drop-down menu next to the timestamp. If your field action does not appear, ensure the correct fields are visible by selecting them from the Fields menu.

Example

[googleExample]
metaKeys=clientip
uri=http://google.com/search?q={$clientip}
label=Google this ip
method=GET

This example enables you to look up the clientip= field via Google. Once you have set up the clientip field through the fields drop-down menu, you can select the new Google this IP link from the drop down next to the clientip field.

http://www.splunk.com/assets/doc-images/3_0_Admin_Fields_fieldactions/googlethis.jpg

[some_custom_search]
metaKeys = ruser,rhost
term=authentication failure | filter ruser={$ruser} rhost={$rhost}
label=Search for other break in attempts by this user
alwaysReplace=true

This example enables you to run another search for authentication failures on the ruser and rhost fields.

Learn more about field_actions.conf, including which other attribute/value pairs are available.

Previous: Create extracted fields via Splunk Web    |    Next: Configure fields.conf

Comments

No comments have been submitted.

Log in to comment.