Splunk® Enterprise

Knowledge Manager Manual

Acrobat logo Download manual as PDF


Splunk Enterprise version 8.1 will no longer be supported as of April 19, 2023. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
Acrobat logo Download topic as PDF

Manage knowledge objects through Settings pages

As your organization uses Splunk software, people add knowledge to the base set of event data indexed within it. You and your colleagues might:

The process of creating knowledge objects starts slowly, but it can become complicated as people use Splunk software for longer periods. It is easy to reach a point where users are creating searches that already exist, adding unnecessary tags, designing redundant event types, and so on. These issues may not be significant if your user base is small. But if they accumulate over time, they can cause unnecessary confusion and repetition of effort.

This chapter discusses how knowledge managers can use the Knowledge pages in Settings to control the knowledge objects in their Splunk deployment. Settings can give an attentive knowledge manager insight into what knowledge objects people are creating, who is creating them, and (to some degree) how people are using them.

With Settings, you can easily:

  • Create knowledge objects when you need to, either "from scratch" or through object cloning.
  • Review knowledge objects as others create them, in order to reduce redundancy and ensure that people are following naming standards.
  • Delete unwanted or poorly-defined knowledge objects before they develop downstream dependencies.
  • Ensure that knowledge objects worth sharing beyond a particular working group, role, or app are made available to other groups, roles, and users of other apps.

Note: This chapter assumes that you have an admin role or a role with an equivalent permission set.

This chapter contains topics that will explain how to:

Managing knowledge using configuration files instead of Settings

In previous releases, Splunk Enterprise users edited configuration files directly to add, update, or delete knowledge objects. Now they can use the Knowledge pages in Settings, which provide a graphical interface for updating those configuration files.

Note: Splunk Cloud users must use the Splunk Web Knowledge pages in Settings to maintain knowledge objects.

Splunk recommends that Splunk Enterprise administrators learn how to modify configuration files. Understanding configuration files is beneficial for the following reasons:

  • Some Splunk Web features make more sense if you understand how things work at the configuration file level. This is especially true for the Field extractions and Field transformations pages in Splunk Web.
  • Managing certain knowledge object types requires changes to configuration files.
  • Bulk deletion of obsolete, redundant, or improperly-defined knowledge objects is only possible with configuration files.
  • You might find that you prefer to work directly with configuration files. For example, if you are a long-time Splunk Enterprise administrator who is already familiar with the configuration file system, you might already be familiar with managing Splunk knowledge using configuration files. Other users rely on the level of granularity and control that configuration files can provide.

The Knowledge Manager manual includes instructions for handling various knowledge object types via configuration files. For more information, see the documentation of those types.

For general information about configuration files in Splunk Enterprise, see the following topics in the Admin manual:

The Admin Manual also contains a configuration file reference, which includes .spec and .example files for all the configuration files in Splunk Enterprise.

Last modified on 23 May, 2017
PREVIOUS
Prerequisites for knowledge management
  NEXT
Monitor and organize knowledge objects

This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.5, 8.0.10, 7.2.1, 7.0.1, 8.0.4, 8.0.9, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.2.0, 8.0.6, 8.0.7, 8.0.8


Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters