Page 1 of 1
Aggregate bandwidth check.
Posted: Thu Jan 07, 2016 2:32 pm
by Atria
I have an internet switch that I would like to be able to take the bandwidth that is consumed by a specific interface which is currently being monitored and reported on, and subtract that bandwidth from the total bandwidth as monitored by a different service, and report that value with perf data so I will have a chart indicating total bandwidth, bandwidth of the interface, and total bandwidth minus that interface. Any suggestion on how that would be configured?
Re: Aggregate bandwidth check.
Posted: Thu Jan 07, 2016 3:17 pm
by rkennedy
How are the checks being performed on your switch? SNMP?
By the sound of this post though, what you'll need to do is build a script of your own to pull the data, do the math, and then set that as a service check.
Re: Aggregate bandwidth check.
Posted: Thu Jan 07, 2016 4:21 pm
by rkennedy
Also - can you please provide a sample of the XML data for these two services in question?
You can find it by navigating to Admin -> Manage Components -> Edit Settings -> Select a user -> Current Service Status - navigate to the URL next to this.
It should look similar to this -
Code: Select all
<servicestatus id="725"><instance_id>1</instance_id><service_id>159</service_id><host_id>144</host_id><host_name>localhost</host_name><name>Total Processes</name><host_display_name/><host_address>127.0.0.1</host_address><display_name>Total Processes</display_name><status_update_time>2016-01-07 13:55:33</status_update_time><status_text>PROCS OK: 94 processes with STATE = RSZDT</status_text><status_text_long/><current_state>0</current_state><performance_data>procs=94;400;500;0;</performance_data><should_be_scheduled>1</should_be_scheduled><check_type>0</check_type><last_state_change>2015-12-15 14:47:46</last_state_change><last_hard_state_change>2015-12-15 14:47:46</last_hard_state_change><last_hard_state>0</last_hard_state><last_time_ok>2016-01-07 13:55:33</last_time_ok><last_time_warning>1969-12-31 18:00:00</last_time_warning><last_time_critical>1969-12-31 18:00:00</last_time_critical><last_time_unknown>1969-12-31 18:00:00</last_time_unknown><last_notification>1969-12-31 18:00:00</last_notification><next_notification>1969-12-31 18:00:00</next_notification><no_more_notifications>0</no_more_notifications><acknowledgement_type>0</acknowledgement_type><current_notification_number>0</current_notification_number><process_performance_data>1</process_performance_data><obsess_over_service>1</obsess_over_service><event_handler_enabled>1</event_handler_enabled><modified_service_attributes>0</modified_service_attributes><event_handler/><check_command>check_local_procs!400!500!RSZDT</check_command><normal_check_interval>5</normal_check_interval><retry_check_interval>1</retry_check_interval><check_timeperiod_id>132</check_timeperiod_id><icon_image/><icon_image_alt/><has_been_checked>1</has_been_checked><current_check_attempt>1</current_check_attempt><max_check_attempts>5</max_check_attempts><last_check>2016-01-07 13:55:33</last_check><next_check>2016-01-07 14:00:33</next_check><state_type>1</state_type><notifications_enabled>1</notifications_enabled><problem_acknowledged>0</problem_acknowledged><flap_detection_enabled>1</flap_detection_enabled><is_flapping>0</is_flapping><percent_state_change>0</percent_state_change><latency>0</latency><execution_time>0.00517</execution_time><scheduled_downtime_depth>0</scheduled_downtime_depth><passive_checks_enabled>1</passive_checks_enabled><active_checks_enabled>1</active_checks_enabled></servicestatus>