Splunk® Enterprise

Knowledge Manager Manual

Download manual as PDF

Splunk Enterprise version 5.0 reached its End of Life on December 1, 2017. Please see the migration information.
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

About lookups and workflow actions

Lookups and workflow actions enable you to enrich and extend the usefulness of your event data through interactions with external resources.

Lookup tables

Lookup tables use information in your events to determine how to add other fields from external data sources such as static tables (CSV files) and Python-based scripts. It's also possible to create lookups that add fields based on time information.

A really basic example of this functionality would be a static lookup that takes the http_status value in an event, matches that value with its definition in a CSV file, and then adds that definition to the event as the value of a new status_description field. So if you have an event where http_status = 503 the lookup would add status_description = Service Unavailable, Server Error to that event.

Of course, there are more advanced ways to work with lookups. For example, you can:

  • Arrange to have a static lookup table be populated by the results of a saved search.
  • Define a field lookup that is based on an external Python script rather than a lookup table. For example, you could create a lookup that uses a Python script that returns an IP address when given a host name, and returns a host name when given an IP address.
  • Create a time-based lookup, if you are working with a lookup table that includes a field value that represents time. For example, this could come in handy if you need to use DHCP logs to identify users on your network based on their IP address and the event timestamp.

For more information, see "Configure field lookups," in this manual.

Workflow actions

Workflow actions enable you to set up interactions between specific fields in your data and other applications or web resources. A really simple workflow action would be one that is associated with an IP_address field, which, when launched, opens an external WHOIS search in a separate browser window based on the IP_address value.

You can also set up workflow actions that:

  • Apply only to particular fields (as opposed to all fields in an event).
  • Apply only to events belonging to a specific event type or group of event types.
  • Are accessed either via event dropdown menus, field dropdown menus, or both.
  • Perform HTTP GET requests, enabling you to pass information to an external web resource, such as a search engine or IP lookup service.
  • Perform HTTP POST requests that can send field values to an external resource. For example, you could design one that sends a status value to an external issue-tracking application.
  • Take certain field values from a chosen event and insert them into a secondary search that is populated with those field values and which launches in a secondary browser window.

For information about setting workflow actions up in Manager, see "Create and maintain workflow actions in Splunk Web", in this chapter.

PREVIOUS
Configure transaction types
  NEXT
Use field lookups to add information to your events

This documentation applies to the following versions of Splunk® Enterprise: 5.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, 5.0.11, 5.0.12, 5.0.13, 5.0.14, 5.0.15, 5.0.16, 5.0.17, 5.0.18


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters