All Apps and Add-ons

Implementing custom task handling across many users: KVStore vs external SQL-DB?

alvaromari83
Path Finder

Hello all!

I'm implementing a "task ticketing model" in my Splunk apps. Based on roles, many users may be assigned to a task, update it, and store new task statuses and other task fields.

I've been doing this with summary indexing (collect commands), but now that many users can generate new task, or operate over the same task concurrently, I'm having concurrency issues (duplicated ids, and other data integrity problems).

As far as I know, apps like Enterprise Security use KVStore to handle this kind of multiuser workflow scenarios, but I'm not sure if this is the most reliable, concurrency failure free, and capable of have relatively big sizes/records (aprox 100000 per year).
Performance is also an important factor.

My other option is to set up an external relational SQL DBMS and use it through DB Connect.

Any light on this to help me would be greatly appreciated!

Thank you!

0 Karma

jcoates_splunk
Splunk Employee
Splunk Employee

http://www.mongodb-is-web-scale.com

You need locking of a structured record... a traditional database is the best tool IMHO.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

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

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...