Building for the Splunk Platform

What should be in my .gitignore for a new app/add-on?

Path Finder

I'm importing an unmaintained app into my own git repo (there is no upstream, AFAICT) and there are a handful of files that are generated and should be ignored in any working copy?

This is what I have so far for my .gitignore:

# Maybe?
# This is added automatically when the app is uploaded, isn't it?

What else?

I realize this is probably somewhere in the documentation, but it's probably spread over several different sources.


So we use git for all configuration files and apps for splunk. Here's what we decided on.


  • .csv - is ignored if any search are generating lookups
  • .pyo - any pythongenerated files
  • local.meta - since this is updated by deployment server
  • !.csv - include any static lookups
  • .idea- since we work on macs
  • DS_Store - since we work on macs

Hope this helps

Get Updates on the Splunk Community!

This Week's Community Digest - Splunk Community Happenings [9.26.22]

Get the latest news and updates from the Splunk Community here! Upcoming User Group Events! &#x1f44f; Check ...

BSides Splunk 2022 - The Call for Papers is now Open!

TLDR; Main Site: CFP Site: CFP Opens: December 15th, ...

Sending Metrics to Splunk Enterprise With the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. The OpenTelemetry project is the second largest ...