strings.conf

strings.conf

strings.conf.spec

# Copyright (C) 2005-2008 Splunk Inc.  All Rights Reserved.  Version 3.0 
# This file contains possible attributes and values you can use to configure text strings
# in strings.conf.
#
# There is a strings.conf in $SPLUNK_HOME/etc/system/default/.  To set custom configurations, 
# place a strings.conf in $SPLUNK_HOME/etc/system/local/.  For examples, see strings.conf.example.
# You must restart Splunk to enable configurations.
#
# To learn more about configuration files (including precedence) please see the documentation 
# located at http://www.splunk.com/base/Documentation/latest/Admin/HowDoConfigurationFilesWork.
#
# CAUTION: You can destroy Splunk's performance by editing this file incorrectly.  Only edit the 
# lowercase strings on the right hand side.  DO NOT edit the upper case resource.  DO NOT change
# any printf formatting strings.
#########################################################################
# String Resources File
#
# STRING NAMES
#
# Full name of resource is stanza_name + attribute name, so
# StringMgr::str("MAP_USAGE") refers to the string value of the USAGE
# attribute in [MAP] stanza.  This allows for short attribute names
# that are unique.
#
# SUBSTITUTION NAMING CONVENTION
#
# After a descriptive name, append two underscores, and then use the
# letters after the % in printf formatting strings, surrounded by
# underscores.  For example "MSG_NAME__D_LU_S" would expect 3 args, a
# %d, %lu, and %s.
#
#########################################################################

strings.conf.example

# Copyright (C) 2005-2008 Splunk Inc.  All Rights Reserved.  Version 3.0 
# This file contains possible attributes and values you can use to configure text strings
# in strings.conf.
#
# To use one or more of these configurations, copy the configuration block into strings.conf 
# in $SPLUNK_HOME/etc/system/local/.  You must restart Splunk to enable configurations.
# To learn more about configuration files (including precedence) please see the documentation 
# located at http://www.splunk.com/base/Documentation/latest/Admin/HowDoConfigurationFilesWork.
#
# CAUTION: You can destroy Splunk's performance by editing this file incorrectly.  Only edit the 
# lowercase strings on the right hand side.  DO NOT edit the upper case resource.  DO NOT change
# any printf formatting strings.
#########################################################################
# String Resources File
#
# STRING NAMES
#
# Full name of resource is stanza_name + attribute name, so
# StringMgr::str("MAP_USAGE") refers to the string value of the USAGE
# attribute in [MAP] stanza.  This allows for short attribute names
# that are unique.
#
# SUBSTITUTION NAMING CONVENTION
#
# After a descriptive name, append two underscores, and then use the
# letters after the % in printf formatting strings, surrounded by
# underscores.  For example "MSG_NAME__D_LU_S" would expect 3 args, a
# %d, %lu, and %s.
#
#########################################################################
[MAP]
VALUE_NOT_FOUND__S = Did not find value for required attribute %s
NO_SAVED_SPLUNK__S = Unable to find saved search with name = %s
USAGE = Usage: (search="subsearch" | saved_search_name)
CANNOT_RUN__S = Unable to run query (%s)

• Was this topic useful?
• Post a comment