Skip to content

Updating splunk.conf in docker-splunk docs #357

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 14, 2020
Merged

Updating splunk.conf in docker-splunk docs #357

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
007c4b8
Updating splunk.conf in docker-splunk docs
Apr 14, 2020
9053d8f
Update ADVANCED.md
alishamayor Apr 14, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 9 additions & 6 deletions docs/ADVANCED.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -230,15 +230,18 @@ User-specified config files are set in `default.yml` by creating a `conf` key un
---
splunk:
conf:
user-prefs:
directory: /opt/splunkforwarder/etc/users/admin/user-prefs/local
content:
general:
default_namespace: appboilerplate
search_syntax_highlighting: dark
- key: user-prefs
value:
directory: /opt/splunkforwarder/etc/users/admin/user-prefs/local
content:
general:
default_namespace: appboilerplate
search_syntax_highlighting: dark
...
```

**NOTE:** Previously, the `splunk.conf` entry supported a dictionary mapping. Both types will continue to work, but it is highly recommended you move to the new array-based type, as this will become the standard.

This generates a file `user-prefs.conf`, owned by the correct Splunk user and group and located in the given directory (in this case, `/opt/splunkforwarder/etc/users/admin/user-prefs/local`).

Following INI format, the contents of `user-prefs.conf` will resemble the following:
Expand Down