All Apps and Add-ons

What are the pros and cons of creating a Splunk app and addon separately?

rshah_splunk
Splunk Employee
Splunk Employee

If developing a new Splunk application, should we prefer creating two separate components, i.e. app and addon or a single bundle? What are the pros and cons? What is the recommended way?

Tags (1)
0 Karma

iandrews_splunk
Splunk Employee
Splunk Employee

Apps are normally for GUI stuff / search heads (dashboards, lookups, etc...)

Add-ons are for knowledge objects, props, transforms, inputs, etc...

If you were to create an add-on that only made a sourcetype CIM compliant, there would be no need for a GUI and, therefore, putting it all in one add-on would be best.

If you wanted to include dashboards, putting the dashboards in an app, and the props/transforms in an add-on, would be best. The admins wouldn't have to install the GUI configs on the indexers, and you could update the two independently.

Get Updates on the Splunk Community!

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

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

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...