Documentation |
Documentation.Interface-CoreEvents-1-7 HistoryHide minor edits - Show changes to output August 05, 2013, at 04:24 PM
by
- Changed line 4 from:
[- Page for other versions: [[Interface-CoreEvents|devel]] [[Interface-CoreEvents-1-9|1.9]] [[Interface-CoreEvents-1-8|1.8]] old versions: 1.7 -] to:
(:allVersions Interface-CoreEvents 1.7:) May 29, 2013, at 11:57 AM
by
- Added lines 1-25:
!!!!!Documentation -> [[Documentation.Manuals|Manuals]] -> [[Documentation.Manual-1-7|Manual 1.7]] -> Core Events (:title Core Events - ver 1.7 :) ---- [- Page for other versions: [[Interface-CoreEvents|devel]] [[Interface-CoreEvents-1-9|1.9]] [[Interface-CoreEvents-1-8|1.8]] old versions: 1.7 -] \\ || %color=#185662%[+'''Core Events v1.7'''+]%% || ||[[Interface-Events-1-7|Prev]] || [[Interface-Statistics-1-7|Next]]|| ---- (:toc-float Table of Content:) Events are exported by the '''OpenSIPS''' core through the Event Interface. ---- !!! Threshold limit exceeded '''Event''': E_CORE_THRESHOLD This event is triggered when a particular action takes longer than a specific threshold. It can be raised when a MySQL or DNS query takes too long, or a SIP message processing goes beyond a specific limit. For more information please see [[http://lists.opensips.org/pipermail/users/2011-February/016918.html | this]] post. Parameters: * '''source''': the source of the event: mysql module, core (for DNS or message processing warnings). * '''time''': the number of micro-seconds the limit has been exceeded * '''extra''': extra information, depending on the source of the event |