Splunk Search

Automated daily lookups

MayDayOne
Explorer

index="URL" NOT [inputlookup A_list_Jan1.csv | fields gtld]
| inputlookup A_listJan1.csv append=true
| dedup gtld
| table gtld
| outputlookup [ | stats count | eval filename=strftime(now(), "B_list%b%d.csv") | return $filename]

QUESTION:
I want to run this search daily. Is there anyway I can automate this search so that "B_list%b%d.csv" gets inserted as the first "inputlookup". This would result in the next days outputlookup as "C_list%b%d.csv".

REASON:
I see 100's of new gtld's on daily basis and I'm making a list of "total gtld's seen".

SECONDARY GOAL:
Create a second daily list of only the new gtld's seen for that day.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

You could make one lookup and include the timestamp of when that ID has been first seen. Should kill both birds with one stone, an overall list and - by filtering - a list per day.

0 Karma

MayDayOne
Explorer

EDIT:
The top two .csv files are the same.

index="URL" NOT [inputlookup A_listJan1.csv | fields gtld]
| inputlookup A_listJan1.csv append=true

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...