Generated properties file
Overwritten property values can be updated in the generated properties file.
You can edit the generated properties file to set up and customize Netcool®/Impact for seasonal events and related
events. The following properties are in the generated properties file.
#
#############################################################################
#### NOI Shared Configuration ####
#############################################################################
#
# If you are updating the Rollup configuration, go to
# The end of the file
# Following section holds the configuration for accessing
# Alerts historical information and storing results
# history_datasource_name Contains the Impact datasourcename
# history_datatype_name Contains the Impact datatype name
# history_database_type Contains the Impact datasource type (Db2, Oracle, MSSQL)
# history_database_table Contains the database table and if required, the schema,
to access the event history
# results_database_type Contains the database type for storing results.
#
# Most likely you do not have to change this configuration
#
history_datasource_name=ObjectServerHistoryDb2ForNOI
history_datatype_name=AlertsHistoryDb2Table
history_database_table=Db2INST1.REPORTER_STATUS
history_database_type=Db2
#
#
#
results_database_type=DERBY
#
# Column name for the analysis
#
history_column_names_analysis=IDENTIFIER
#
# The column name where the timestamp associated with the records is stored
#
history_column_name_timestamp=FIRSTOCCURRENCE
#
#
#
history_db_timestampformat=yyyy-MM-dd HH:mm:ss.SSS
configuration_db_timestampformat=yyyy-MM-dd HH:mm:ss.SSS
#
#############################################################################
#### Seasonality Only Configuration ####
#############################################################################
#
# Will only save and process events of this confidence level or higher
#
save_event_threshold=.85
#
# Used in determining the confidentialiy level ranges, by determining the
threshold values.
# level_threshold_high Level is high, when confidentiality is greater than
or equal to
# level_threshold_medium Level is medium, when confidentiality is greater
than or equal to
# level_threshold_low Level is low, when confidentiality is greater than or
equal to
# If the confidentiality doesn't meet any of these conditions, level will be
set to unknown.
#
level_threshold_high=99
level_threshold_medium=95
level_threshold_low=0
#
# Rollup configuration adds additional information to the Seasonal Report data
# number_of_rollup_configuration Contains the number of additional rollup
configuration
# rollup_ <number where its 1 to n >_column_nameContains the column name from
which the data is retreived
# rollup_ <number where its 1 to n >_type Contains the type value
# rollup_ <number where its 1 to n >_display_name A name that needs to be
defined in the UI
# Types can be defined as follows :
# MAX, MIN, SUM, NON_ZERO, DISTINCT and EXAMPLE
# MAX: The maximum value observed for the column, if no value is ever seen
this will default to Integer.MIN_VALUE
# MIN: The minimum value observed for the column, if no value is ever seen
this will default to Integer.MAX_VALUE
# SUM: The sum of the values observed for the column.
# NON_ZERO: A counting column, that counts "Non-Zero"/"Non-Blank"
occurrences of events, this can be useful to
# track the proportion of events that have been actioned,
or how many events had a ticket number associated
# with them.
# DISTINCT: The number of distinct values that have been seem for this key,
value pair
# EXAMPLE: Show the first non-blank "example" of a field that contained this
key, useful when running seasonality on a
# field that can't be accessed, such as ALERT_IDENTIFIER, and you want an
example human readable
# SUMMARY to let you understand the type of problem
#
number_of_rollup_configuration=2
rollup_1_column_name=SEVERITY
rollup_1_type=MIN
rollup_1_display_name=MINSeverity
rollup_2_column_name=SEVERITY
rollup_2_type=MAX
rollup_2_display_name=MAXSeverity
#
#############################################################################
#### Related Events Only Configuration ####
#############################################################################
#
# Rollup configuration adds additional information to the Related Events data
# reevent_number_of_rollup_configuration Contains the number of additional
rollup configuration
# reevent_rollup_ <number where its 1 to n >_column_nameContains the column
name from which the data is retrieved
# reevent_rollup_ <number where its 1 to n >_type Contains the type value
# reevent_rollup_ <number where its 1 to n >_display_name A name that needs
to be defined in the UI
# reevent_rollup_ <number where its 1 to n >_actionable Numeric only column
that determines the weight for probable root cause
# Types can be defined as follows :
# MAX, MIN, SUM, NON_ZERO, DISTINCT and EXAMPLE
# MAX: The maximum value observed for the column, if no value is ever
seen this will default to Integer.MIN_VALUE
# MIN: The minimum value observed for the column, if no value is ever
seen this will default to Integer.MAX_VALUE
# SUM: The sum of the values observed for the column.
# NON_ZERO: A counting column, that counts "Non-Zero"/"Non-Blank"
occurrences of events, this can be useful to
# track the proportion of events that have been actioned, or
how many events had a ticket number associated
# with them.
# DISTINCT: The number of distinct values that have been seem for this
key, value pair
# EXAMPLE: Show the first non-blank "example" of a field that contained
this key, useful when running Seasonality on a
# field that can't be accessed, such as ALERT_IDENTIFIER, and you want
an example human readable
# SUMMARY to let you understand the type of problem
#
reevent_number_of_rollup_configuration=3
reevent_rollup_1_column_name=ORIGINALSEVERITY
reevent_rollup_1_type=MAX
reevent_rollup_1_display_name=MAXSeverity
reevent_rollup_1_actionable=true
reevent_rollup_2_column_name=ACKNOWLEDGED
reevent_rollup_2_type=NON_ZERO
reevent_rollup_2_display_name=Acknowledged
reevent_rollup_2_actionable=true
reevent_rollup_3_column_name=ALERTGROUP
reevent_rollup_3_type=EXAMPLE
reevent_rollup_3_display_name=AlertGroup
reevent_rollup_3_actionable=false
#
# Group Information adds additional group information under the Show Details ->
Group More Information portion of the UI
# reevent_num_groupinfo Contains the number of group information columns to
display
# reevent_groupinfo_ <number where its 1 to n >_columnContains the column
name from which the data is retrieved
# The following columns are allowed :
# PROFILE, EVENTIDENTITIES, INSTANCES, CONFIGNAME, TOTALEVENTS,
UNIQUEEVENTS, REVIEWED, GROUPTTL
# PROFILE: The relationship profile, or strength of the group.
# EVENTIDENTITIES: A comma separated list that creates the event identity.
# INSTANCES: The total number of group instances.
# CONFIGNAME: The configuration name the group was created under.
# TOTALEVENTS: The total number of events within the group.
# UNIQUEEVENTS: The total number of unique events within the group.
# REVIEWED: Whether the group has been reviewed by a user or not.
# GROUPTTL: The number of seconds the group will stay active after the
first event occurs.
#
reevent_num_groupinfo=3
reevent_groupinfo_1_column=PROFILE
reevent_groupinfo_2_column=EVENTIDENTITIES
reevent_groupinfo_3_column=INSTANCES
#
# Event Information adds additional event information under the Show Details ->
Event More Information portion of the UI
# reevent_num_eventinfo Contains the number of event information columns to
display
# reevent_eventinfo_ <number where its 1 to n >_columnContains the column name
from which the data is retrieved
# The following columns are allowed :
# PROFILE, INSTANCES, EVENTIDENTITY, EVENTIDENTITIES, CONFIGNAME, and GROUPNAME
# PROFILE: The relationship profile, or strength of the related event.
# INSTANCES: Total number of instance for the related event.
# EVENTIDENTITY: The unique event identity for the related event.
# EVENTIDENTITIES: A comma separated list that creates the event identity.
# CONFIGNAME: The configuration name the related event was created under.
# GROUPNAME: The group name the related event is created under.
#
reevent_num_eventinfo=1
reevent_eventinfo_1_column=INSTANCES
#
##################################################################################
# The following properties are used to configure event pattern creation ##
# type.resourcelist=<columns include information. Comma separated list > ##
# type.servername.column=<SERVERNAME column name if different than default> ##
# type.serverserial.column=<SERVERSERIAL column name if different than default> ##
# type.default.eventid=<default event identities when there is no mactch ##
# found in the types configuration. Comma separated list ##
# The id should not include a timestamp component. ##
# type.default.eventtype=<default event type when there is no match ##
# found in the types configuration. ##
# type index starts with 0 ##
# type_number_of_type_configurations=number of type configurations ##
# type.index.eventid=event identity column name ##
# type.index.eventtype=event column includes the type to use ##
# type.index.filterclause=History DB filter to filter events to find the types ##
# type.index.osfilterclause=ObjectServer filter tp filter matching events types ##
# ##
# ##
# NOTE : It is recommended to create database index(s) on the reporter status ##
# table for the fields used in the filtercaluse to speed the query(s). ##
# Example to create an index: ##
# create index types_index on db2inst1.reporter_stuats (Severity) ##
# ##
# ##
#Use the following as an example creating one type only ##
# ##
#type_number_of_type_configurations=1 ##
#type.0.eventid=NODE,SUMMARY,ALERTGROUP ##
#type.0.eventtype=ACMEType ##
#type.0.filterclause=Vendor =( 'ACME' ) ##
#type.0.osfilterclause=Vendor = 'ACME' ##
##################################################################################
type.resourcelist=NODE
type.default.eventid=IDENTIFIER
type.default.eventtype=ALERTGROUP
type.servername.column=SERVERNAME
type.serverserial.column=SERVERSERIAL
type_number_of_type_configurations=1
type.0.eventid=SUMMARY
type.0.eventtype=ALERTGROUP
type.0.filterclause=( Severity >=3 )
type.0.osfilterclause=Severity >=3
#
##################################################################################
# The following properties are used to configure Name Similarity NS ##
##################################################################################
name_similarity_feature_enable=true
name_similarity_default_pattern_enable=false
name_similarity_default_threshold=0.9
name_similarity_default_lead_restriction=1
name_similarity_default_tail_restriction=0