Last updated: July 20th, 2011
Apps
Namespaces
- Lookups do not have default and local namespaces
- As a result, upon upgrade a mutable lookup could be replaced by the default lookup that ships with the app
- If knowledge objects in two different apps share the same stanza name and are exported globally, configuration file precedence will dictate which object is effective.
- As a result, collisions, overridden settings, and other unexpected or unintended behavior is possible
- Certain objects such as inputs, outputs, and indexes have explicit global scope, no matter where or how they are defined
Templates
- Prior to Splunk version 4.2.3, Mako templates present in the ./appserver/templates directory cannot be referenced in views
- As a result, it is not possible to package mako templates with apps in Splunk versions 4.0 through 4.2.2
Modules
Access Control
- Modules are not governed by role-based access control
- As a result, there is no way to restrict what users and roles can access or utilize a module in an app
Namespaces
- Modules are all part of a global namespace, including modules defined in individual apps
- As a result, if two modules with the same name exist on the same Splunk instance, unexpected behavior may occur due to namespace collisions