Two commands so far.
Given the path to a csv file somewhere in SPLUNK_HOME, tag all events passed in with the values found in the specified field.
This is useful for counting matches of certain terms in raw in events, even if they can't easily be extracted into fields.
The raw text of each event will be tested for each value of field in the csv file, and if a match is found, that field is attached the event.
* | matchfieldfromcsv csv="/etc/apps/foo/test.csv" field="bar"
* [|inputlookup users | rename username as search | fields + search | format ] | matchfieldfromcsv csv="etc/apps/search/lookups/users.csv" field=username | stats count by username
Given a list of csvs that have been created with outputcsv, each of the csv files is attached to a message and mailed to the address provided.
my great search | outputcsv foo.csv | emailcsvs to="firstname.lastname@example.org" csvs="foo.csv"
or more complicated:
my great search | outputcsv foo.csv | append maxtime=3600 [search my other great search | outputcsv bar.csv] | emailcsvs to="email@example.com" csvs="foo.csv,bar.csv" delete_on_exit=true
I will add other commands as it comes up, or per suggestion.
Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.