opCharts Configuration

The configuration options for opTrend are stored in a text file /usr/local/omk/conf/opCommon.nmis.

Configuration items that are not application specific are detailed on the opCommon Configuration page.

Common Settings to Consider Adjusting

The items below are commonly changed by customers.

Section	Name	Original Value	Description
optrend	optrend_seds_control_mutliplier	3
optrend	optrend_db_name	optrend	The name of your MongoDB database.
optrend	optrend_process_condition_in_nmis	true
optrend	optrend_gui_period_values	["8h", "12h", "1d", "2d", "5d", "7d", "14d", "30d", "60d", "90d", "180d"]

The opTrend section of opCommon.nmis is for opTrend specific configuration items only.

Section	Name	Original Value	Possible Values
optrend	optrend_billboard_topn	25	<integer>
optrend	optrend_db_name	optrend
optrend	optrend_db_seds_collection_size	16106127360	<integer>
optrend	optrend_db_write_concern	1	<integer>
optrend	optrend_exceptions_to_make_condition	3	<integer>
optrend	optrend_gui_node_summary_list	['name','group','host','location','nodeVendor','nodeModel','sysDescr']
optrend	optrend_gui_period_values	["8h", "12h", "1d", "2d", "5d", "7d", "14d", "30d", "60d", "90d", "180d"]
optrend	optrend_gui_refresh_time	3600	<integer>
optrend	optrend_maxthreads	10	<integer>
optrend	optrend_mthread	1	<integer>
optrend	optrend_process_condition_in_nmis	true	true, false
optrend	optrend_seds_condition_table	{'Fatal' => 10, 'Critical' => 7, 'Major' => 5, 'Minor' => 3, 'Warning' => 1}
optrend	optrend_seds_control_mutliplier	3	<integer>
optrend	optrend_seds_expire_after_seconds	606024*21
optrend	optrend_seds_weeks_of_history	26	<integer>
optrend	optrend_topn_sections	[ {"Node Health" => [{ 'cpuLoad' =>'cpu' }, { 'MemoryUtil' =>'memory' },{ 'tcpCurrEstab' => 'tcp'}, {'hrSystemProcesses' => 'processes'} ]}, {'Interface Trend' => [{ 'ifInUtil' =>'interface' }, { 'ifOutUtil' =>'interface' },{ 'ifInErrors' =>'packets' },{ 'ifOutErrors' =>'packets' },{ 'ifInDiscards' =>'packets' }, { 'ifOutDiscards' =>'packets' }]}]