Closed Bug 1363498 Opened 8 years ago Closed 7 years ago

Move nagios SIP registration monitoring from Asterisk pbx to reg.jiveip.net (YVR)

Categories

(Infrastructure & Operations :: MOC: Service Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1363501

People

(Reporter: freshness, Assigned: vinh)

Details

Nagios is alerting in #teamcoco that the VH20 devices are not reaching pbx1. These devices have already been cutover to the new Jive SIP server(reg.jiveip.net) Tue 19:00:41 UTC [5910] [networkops] pbx1.voip.yvr1.mozilla.com:ClearOne devices yvr is CRITICAL: ['ClearOne device failed: 75231', 'ClearOne device failed: 75239'] (http://m.mozilla.org/ClearOne+devices+yvr)
Assignee: nobody → vhua
I'll remove the nagios check in the meantime.
Status: NEW → ASSIGNED
diff --git a/modules/nagios4/manifests/prod/mozilla/services.pp b/modules/nagios4/manifests/prod/mozilla/services.pp index ae83358c85..b9157d2812 100644 --- a/modules/nagios4/manifests/prod/mozilla/services.pp +++ b/modules/nagios4/manifests/prod/mozilla/services.pp @@ -308,19 +308,19 @@ class nagios4::prod::mozilla::services { ] } }, - 'asterisk_clear_one_yvr' => { - service_description => 'ClearOne devices yvr', - servicegroups => 'asterisk-services', - contact_groups => 'teamcoco', - check_command => 'check_clear_one!75231/75239', - hostgroups => $nagiosbot ? { - 'nagios-scl3' => [ - 'yvr1-asterisk' - ], - default => [ - ] - } - }, +# 'asterisk_clear_one_yvr' => { +# service_description => 'ClearOne devices yvr', +# servicegroups => 'asterisk-services', +# contact_groups => 'teamcoco', +# check_command => 'check_clear_one!75231/75239', +# hostgroups => $nagiosbot ? { +# 'nagios-scl3' => [ +# 'yvr1-asterisk' +# ], +# default => [ +# ] +# } +# }, 'asterisk_clear_one_mtv' => { service_description => 'ClearOne devices mtv', servicegroups => 'asterisk-services',
Waiting on Jive to hopefully provide an API soon for us to write a monitor for this.
<justdave> Engineer says the framework for the API they've been developing is in place, but an appropriate function to do that is not in it yet. Dev guys are working out specs and hope to get in touch with us soon to work out use case/any special needs before implementing it
QA Contact: lypulong → kferrando
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.