Thanks a lot Razvan. Will try them and keep the group posted about the results.
On Wed, Jan 11, 2017 at 2:01 PM, Răzvan Crainea <[email protected]> wrote: > Hi, Chandan! > > Is there any way you could monitor the endpoints? If so, you can use the > load balancer pinging, that will automatically disable the end point when > it is not responding, and monitor the state over MI. > > If there is no way you monitor the endoints, you could: > 1. Check the tm transactions ended with 4xx status. If you see a spike, > send an alert. The comand to do that is: > opensipsctl fifo get_statistics 4xx_transactions > > 2. Create your own statistics in the script based on the endpoint. In the > script, do something like this: > if (t_check_status("486")) > update_stat("$stat(tran_486_$si)", "+1"); > > Again, monitor these statistics over MI and if you see spikes, send alerts. > > These are the solutions I am thinking of. Hope they are helpful. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 01/11/2017 08:51 AM, Chandan PR wrote: > > Hi, > > Recently one of our endpoints stopped responding and due to which nearly > almost all of the calls ended up in 486. > > Is there any functions we can use to monitor the response codes per node > over a duration so that we can raise an alert to take corrective actions in > such cases. > > *The version of OpenSips we are using is 1.9.x* > > Regards, > Chandan > > > _______________________________________________ > Users mailing > [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
