Splunk Dev

Where to create custom app?

patelmc
Explorer

I am not using deployment server in our environment yet. I have non-clustered search head and three indexers. If I want to create custom app where should I create it. on search head server or app server (indexer)?

I have same setup in A side (primary) and B side (standby). Both active - active.
A side - one search head and three app servers (indexers).
B side - one search head and three app servers (indexers).

I know this will consume double license but that's the requirement.

Tags (1)
0 Karma

diogofgm
SplunkTrust
SplunkTrust

It will depend on the functionality of the app you want to create.

Example:
If it contains knowledge objects (views/dashboards, reports, alerts, etc.) it should go in the search head.
If it contains index time operations (e.g. data routing, anonymization, etc) it should go into Indexers/heavy forwarder

Check Splunk's guide to app development:
http://dev.splunk.com/view/SP-CAAAFD7#createapp

------------
Hope I was able to help you. If so, some karma would be appreciated.
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Where the app goes depends on what the app does. Apps that will contain search-time objects like dashboards, alerts, and reports go on search heads. Apps that contain index-time properties for processing events (props.conf and transforms.conf) go on indexers. Apps that define inputs should go on forwarders.

Wherever you put the app, you will have to copy it to the opposite manually, of course.

---
If this reply helps you, Karma would be appreciated.
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!

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 ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...