Documentation

Documentation.Interface-CoreEvents History

Show minor edits - Show changes to markup

July 21, 2015, at 11:58 AM by liviu -
Changed lines 1-61 from:
Documentation -> Manuals -> Manual devel -> Core Events

(:title Core Events - devel :)


Page for other versions: devel 1.9 1.8 old versions: 1.7


Core Events devel
PrevNext

(: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 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

Private memory threshold exceeded

Event: E_CORE_PKG_THRESHOLD

This event is triggered when the private memory usage goes above a threshold limit, specified by the event_pkg_threshold the core parameter. It warns external applications about low values of free private memory.

Parameters:

  • usage: the percentage of private memory usage. Can have values between event_pkg_threshold and 100.
  • threshold: the event_pkg_threshold specified in the script.
  • used: the amount of private memory used.
  • size: the total amount of private memory.
  • pid: the pid of the process that raises the event.

Note: If the event_pkg_threshold is not specified or 0, then this event is disabled.

Shared memory threshold exceeded

Event: E_CORE_SHM_THRESHOLD

This event is triggered when the shared memory usage goes above a threshold limit, specified by the event_shm_threshold the core parameter. It warns external applications about low values of free shared memory.

Parameters:

  • usage: the percentage of private memory usage. Can have values between event_shm_threshold and 100.
  • threshold: the event_shm_threshold specified in the script.
  • used: the amount of private memory used.
  • size: the total amount of private memory.

Note: If the event_shm_threshold is not specified or 0, then this event is disabled.

to:

(:redirect Documentation.Interface-CoreEvents-2-2 quiet=1:)

May 29, 2013, at 11:50 AM by 109.99.235.212 -
Added line 43:
Changed lines 45-46 from:
to:
Changed lines 59-61 from:

Note: If the event_shm_threshold is not specified or 0, then this event is disabled.

to:

Note: If the event_shm_threshold is not specified or 0, then this event is disabled.

May 29, 2013, at 11:44 AM by 109.99.235.212 -
Deleted lines 16-17:

This documentation is for OpenSIPS trunk/devel version.

May 29, 2013, at 11:43 AM by 109.99.235.212 -
Changed lines 1-2 from:

Documentation? -> Interface -> Core Events

to:
Documentation -> Manuals -> Manual devel -> Core Events

(:title Core Events - devel :)

Added lines 4-12:

Page for other versions: devel 1.9 1.8 old versions: 1.7


Core Events devel
PrevNext

Added lines 14-15:
May 10, 2013, at 03:19 PM by 109.99.235.212 -
Changed lines 1-2 from:

Resources -> Documentation -> CookBooks -> Core Events

to:

Documentation? -> Interface -> Core Events


April 24, 2013, at 07:22 PM by 109.99.235.212 -
Added lines 1-47:

Resources -> Documentation -> CookBooks -> Core Events

(:toc-float Table of Content:) Events are exported by the OpenSIPS core through the Event Interface.

This documentation is for OpenSIPS trunk/devel version.


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 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

Private memory threshold exceeded

Event: E_CORE_PKG_THRESHOLD

This event is triggered when the private memory usage goes above a threshold limit, specified by the event_pkg_threshold the core parameter. It warns external applications about low values of free private memory.

Parameters:

  • usage: the percentage of private memory usage. Can have values between event_pkg_threshold and 100.
  • threshold: the event_pkg_threshold specified in the script.
  • used: the amount of private memory used.
  • size: the total amount of private memory.
  • pid: the pid of the process that raises the event.

Note: If the event_pkg_threshold is not specified or 0, then this event is disabled.

Shared memory threshold exceeded

Event: E_CORE_SHM_THRESHOLD

This event is triggered when the shared memory usage goes above a threshold limit, specified by the event_shm_threshold the core parameter. It warns external applications about low values of free shared memory.

Parameters:

  • usage: the percentage of private memory usage. Can have values between event_shm_threshold and 100.
  • threshold: the event_shm_threshold specified in the script.
  • used: the amount of private memory used.
  • size: the total amount of private memory.

Note: If the event_shm_threshold is not specified or 0, then this event is disabled.


Page last modified on July 21, 2015, at 11:58 AM