<commit_before>#
# This properties file allows you to set global properties for the opennms
# application.  These properties will be set as system properties at the
# beginning of Java startup.  Any properties set on the Java command-line
# with -Dproperty=value will be overridden by these values.
#

#
# OpenNMS provides two different SNMP implementations.  JoeSNMP is the
# original OpenNMS # SNMP Library and provides SNMP v1 and v2 support.
# SNMP4J is a new 100% Java SNMP library # that provides support for SNMP
# v1, v2 and v3.  
#
# To enable the JoeSnmp library uncomment the following line.
#org.opennms.snmp.strategyClass=org.opennms.netmgt.snmp.joesnmp.JoeSnmpStrategy
#
# The SNMP4J library is currently the default.  But can also be set with
# the following line.
#
# Default:
#org.opennms.snmp.strategyClass=org.opennms.netmgt.snmp.snmp4j.Snmp4JStrategy

#
# On very large systems the OpenNMS default mechanism of storing one data
# source per RRD file can be very I/O Intensive.  Many I/O subsystems fail
# to keep up with the vast amounts of data that OpenNMS can collect in this
# situation.  We have found that in those situations having fewer large files
# with multiple data sources in each performs better than many smaller files,
# each with a single data source.  This option enables all of the data sources
# belonging to a single collection group to be stored together in a single
# file.  To enable this setting uncomment the below line and change it to
# 'true'.  Also note that the snmp-graph.properties will need to change as
# it indicates which files need to exist for each graph.  Look in 
# ${opennms.home}/etc/examples/store-by-group-snmp-graph.properties for an
# example of the changes.
# 
# Default:
#org.opennms.rrd.storeByGroup=false

#
# Though this is not strictly an OpenNMS property this is a setting that you
# may need to set if you are using the distributed monitor either via webstart
# or the command-line remote poller.  In these cases, all of the remote
# monitors need a hostname or IP address they can resolve to locate the
# central OpenNMS server.  This code uses Java's RMI protocol to communicate
# and needs to know the name the client will use to connect.  This will be
# especially true if the client must connect to the server thru a firewall.
#
# The default behavior is for it to pick one of the IP addresses of the server
# host.
#
#java.rmi.server.hostname=<some server ip address>

# RRD base directory 
rrd.base.dir=@install.share.dir@/rrd

# RRD binary path (only used if the JniRrdStrategy is used)
rrd.binary=@install.rrdtool.bin@<commit_msg>Add a default value for the opennms.ticketer.plugin<commit_after>#
# This properties file allows you to set global properties for the opennms
# application.  These properties will be set as system properties at the
# beginning of Java startup.  Any properties set on the Java command-line
# with -Dproperty=value will be overridden by these values.
#

#
# OpenNMS provides two different SNMP implementations.  JoeSNMP is the
# original OpenNMS # SNMP Library and provides SNMP v1 and v2 support.
# SNMP4J is a new 100% Java SNMP library # that provides support for SNMP
# v1, v2 and v3.  
#
# To enable the JoeSnmp library uncomment the following line.
#org.opennms.snmp.strategyClass=org.opennms.netmgt.snmp.joesnmp.JoeSnmpStrategy
#
# The SNMP4J library is currently the default.  But can also be set with
# the following line.
#
# Default:
#org.opennms.snmp.strategyClass=org.opennms.netmgt.snmp.snmp4j.Snmp4JStrategy

#
# On very large systems the OpenNMS default mechanism of storing one data
# source per RRD file can be very I/O Intensive.  Many I/O subsystems fail
# to keep up with the vast amounts of data that OpenNMS can collect in this
# situation.  We have found that in those situations having fewer large files
# with multiple data sources in each performs better than many smaller files,
# each with a single data source.  This option enables all of the data sources
# belonging to a single collection group to be stored together in a single
# file.  To enable this setting uncomment the below line and change it to
# 'true'.  Also note that the snmp-graph.properties will need to change as
# it indicates which files need to exist for each graph.  Look in 
# ${opennms.home}/etc/examples/store-by-group-snmp-graph.properties for an
# example of the changes.
# 
# Default:
#org.opennms.rrd.storeByGroup=false

#
# Though this is not strictly an OpenNMS property this is a setting that you
# may need to set if you are using the distributed monitor either via webstart
# or the command-line remote poller.  In these cases, all of the remote
# monitors need a hostname or IP address they can resolve to locate the
# central OpenNMS server.  This code uses Java's RMI protocol to communicate
# and needs to know the name the client will use to connect.  This will be
# especially true if the client must connect to the server thru a firewall.
#
# The default behavior is for it to pick one of the IP addresses of the server
# host.
#
#java.rmi.server.hostname=<some server ip address>

# RRD base directory 
rrd.base.dir=@install.share.dir@/rrd

# RRD binary path (only used if the JniRrdStrategy is used)
rrd.binary=@install.rrdtool.bin@

#
# The ticket plugin implementation to use to create tickets via the Alarm details
# pages (if configured).  The NullTicketerPlugin just does nothing when attempting
# to create tickets.
opennms.ticketer.plugin=org.opennms.netmgt.ticketd.NullTicketerPlugin

{'fraction_non_alphanumeric': 0.057365182772348894, 'fraction_numerical': 0.004343105320304018, 'mean_word_length': 4.170252572497661, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4936120', 'n_tokens_mistral': 1608, 'n_tokens_neox': 1582, 'n_words': 776}