Databases Reference
In-Depth Information
A few things to note from this overly simplified example are as follows:
1. Your CSS classes may end up merging with styles included by Splunk in
unexpected ways. Using the developer tools in any modern browser will
help greatly.
2. The navigation and dashboard title were excluded for brevity. They would
normally go where we see
<!-- chrome here -->
. This is interesting
because there are cases where you would want to exclude the navigation;
something that cannot be done with simple XML.
3. The static files, such as
application.css
, can be edited directly on the
filesystem, and the changes will be seen immediately. This is not true of the
dashboard XML file. We will cover these locations later in the
App directory
structure
section.
Object permissions
Almost all objects in Splunk have permissions associated with them. The permissions
essentially have the following three options:
•
Private
: Only the user that created the search can see or use the object,
and only in the app where it was created
•
App
: All users that have permission to read an object may use that object
in the context of the app that contains that object
•
Global
: All users that have permission to read an object may use that object
in any app
Search WWH ::
Custom Search