Deployment Architecture

Replace data on each import?

jcooperFossil
Path Finder

I'm using Best Practical "Request Tracker 4" as my ticketing system, and I'm trying to pull the data in to Splunk for dashboarding purposes.

Currently I have it set up on DBConnect, but there is a horrible one-to-many database set up where the same field names are used in multiple sourcetypes, making the Splunk searches having to use a lot of join and append commands. The other issue is the lastupdated field vs the createddate field and getting accurate information.

We've found a better way, but I need help on improving it. Currently we:
1. Delete the current index of data since the values of recent tickets have probably changed since the last import
2. Export the CSV
3. Import in to Splunk

Is there a way I can have a Splunk UF monitor a directory, import the CSV into perhaps a summary index, overwriting the old data with each import? Does the UF allow importing into a lookup?

NOTE: I'm using Splunk Cloud, and have Heavy Forwarders on premise.

Tags (1)
0 Karma
Get Updates on the Splunk Community!

Expert Tips from Splunk Professional Services, Ensuring Compliance, and More New ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Observability Release Update: AI Assistant, AppD + Observability Cloud Integrations & ...

This month’s releases across the Splunk Observability portfolio deliver earlier detection and faster ...

Stay Connected: Your Guide to February Tech Talks, Office Hours, and Webinars!

💌Keep the new year’s momentum going with our February lineup of Community Office Hours, Tech Talks, ...