KV Store Tools Redux - Splunk App by Deductiv

Utilities for the Splunk App Key-Value Store

Rewrite of Gemini KV Store Tools

The KV Store Tools for Splunk app includes the following features:

Generating Commands

• KV Store Backup: Backup KV Store collections to the file system on the search head.
• KV Store Restore: Restore KV Store collections from backup jobs¹. Lists all existing backups in the default path if no arguments are given.
• KV Store Push: Copy KV Store collections from the local Splunk search head to a remote instance (SH/SHC)¹.
• KV Store Pull: Copy KV Store collections from a remote Splunk search head (SH/SHC) to the local instance¹.
• Delete Key: Delete KV Store records from a collection based on user input.

Streaming Commands

• Create Foreign Key: Creates an entry in a lookup and appends the resulting _key value to the current search results. Useful for writing linked entries in two lookups.
• Delete Keys: Delete KV Store records from a collection based on _key values in search results.

Alert Actions

• Send to Collection: Similar to outputlookup, but can be toggled on/off by users that have permissions to edit search jobs without modifying the search. This functionality has been implemented by Splunk directly into the product since this was written.

[1]: Deletes the collections from the target host before writing (unless otherwise specified).

---

Command Usage

KV Store Backup

Back up a KV Store collection to disk on the local node. The backup process will write one or more .json or .json.gz files (one for each collection). For search head clusters, it's recommended to have a shared volume (e.g. NFS) among all nodes for backups to reliably enforce the retention policy and the kvstorerestore command functionality.

This functionality is implemented through a generating search command. Syntax:

| kvstorebackup app="app_name" collection="collection_name" path="/data/backup/kvstore" global_scope="false"  

Arguments:

• (Optional) app: - Set the app in which to look for the collection(s). (Default: All)
• (Optional) path: - Set the directory path for the output files. (Default: the the setting in the app Setup page)
• (Optional) global_scope: [true|false] - Specify the whether or not to include all globally available collections. (Default: false)
• (Optional) collection: - Specify the collection to backup. (Default: All)
• (Optional) compression: [true|false] - Specify whether or not to compress the backups. (Default: false)

KV Store Restore

Restore a KV Store collection backup file to the local node. Uses the filename to determine the app name and collection to write the data to. By default, the restore process will delete the KV Store collection and overwrite it with the contents of the backup unless append=true is set. Running the search command with no arguments will list existing backups in the default path.

This functionality is implemented through a generating search command. Syntax:

| kvstorerestore filename="/backup/kvstore/app_name#collection_name#20170130*"  

Arguments:

• (Optional) filename: - Specify the file to restore the data from.
• (Optional) append: [true|false] - Specify whether or not to append records to the target KV Store collections. (Default: false - deletes the collection prior to restoring)

KV Store Push

Upload local KV Store collection(s) to one or more target instances. Configure your remote Splunk credentials in the Setup page. The replication process will delete the target KV Store collection and overwrite it with the local contents unless append=true is set.

This functionality is implemented through a generating search command. Syntax:

| kvstorepush app="<app_name>" collection="<collection_name>" global_scope="[true|false]" append="[true|false]" target="<remote_hosts>"  

Arguments:

• (Required) target: - Specify the hostnames in a comma separated list to upload collections to.
• (Optional) port: - Specify the target splunkd port on the remote host. (Default: 8089)
• (Optional) app: - Specify the app to find the collection(s) within. (Default: All)
• (Optional) global_scope: [true|false] - Specify the whether or not to include all globally available collections. (Default: false)
• (Optional) collection: - Specify the collection to migrate. (Default: All)
• (Optional) append: [true|false] - Specify whether or not to append records to the target KV Store collections. (Default: false - deletes the collection prior to migrating)

KV Store Pull

Download local KV Store collection(s) from another instance to the local one. Configure your remote Splunk credentials in the Setup page. The replication process will delete the local KV Store collection and overwrite it with the remote contents unless append=true is set.

This functionality is implemented through a generating search command. Syntax:

| kvstorepull app="<app_name>" collection="<collection_name>" global_scope="[true|false]" append="[true|false]" target="<remote_host>"  

Arguments:

• (Required) target: - Specify the hostname to download collections from.
• (Optional) port: - Specify the target splunkd port on the remote host. (Default: 8089)
• (Optional) app: - Specify the app to find the collection(s) within. (Default: All)
• (Optional) global_scope: [true|false] - Specify the whether or not to include all globally available collections. (Default: false)
• (Optional) collection: - Specify the collection to migrate. (Default: All)
• (Optional) append: [true|false] - Specify whether or not to append records to the target KV Store collections. (Default: false - deletes the collection prior to migrating)

KV Store Create Foreign Key

Writes data from the search into a new KV store collection record and returns the record's _key value into the search as a new field. The _key value becomes a foreign key reference in the search results, which can be written to a second lookup using outputlookup.

This functionality is implemented through a streaming search command. Syntax (example):

search <events> | kvstorecreatefk collection="<collection1_name>" outputkeyfield="<key_field_name>" | outputlookup append=t <collection2_name>

Arguments:

• (Required) collection: - Specify the collection to create the new record within.
• (Optional) app: - Specify the app to find the collection(s) within. (Default: current app)
• (Optional) outputkeyfield: - Specify the output field to write the new key value to. (Default: _key)
• (Optional) outputvalues: - Specify the fields/values to write to the collection record (e.g. lookup_fieldname=$event_field$). Uses the first non-null field value in the search results. (Default: None)
• (Optional) append: [true|false] - Specify whether or not to append records to the target KV Store collections. (Default: false - deletes the collection prior to migrating)

KV Store Delete Keys

Delete multiple KV Store collection records based on the _key value from the search result input.

This functionality is implemented through a streaming search command. Syntax (example):

| inputlookup lookup_name where domain="*splunk.com" | deletekeys collection="collection_name"  

Arguments:

• (Optional) app: - Specify the app to find the collection within. (Default: All)
• (Required) collection: - Specify the collection to delete the data from.

KV Store Delete Key

Deletes a specific record from a KV Store collection based on _key value.

This functionality is implemented through a generating search command. Syntax:

| deletekey collection="collection_name" key="key_value"  

Arguments:

• (Optional) app: - Specify the app to find the collection within. (Default: All)
• (Required) collection: - Specify the collection to delete the data from.
• (Required) key: - Specify the value for the _key field in the collection record.