From openSIPS

Documentation: Core Events - 3.0

Documentation -> Manuals -> Manual 3.0 -> Core Events

Pages for other versions: devel 3.3 3.2 3.1 Older versions: 3.0 2.4 2.3 2.2 2.1 1.11 1.10 1.9 1.8 1.7


Core Events v3.0
PrevNext

Table of Content (hide)

  1. 1. Threshold limit exceeded
  2. 2. Private memory threshold exceeded
  3. 3. Shared memory threshold exceeded
  4. 4. Process Auto-Scaling (upscale and downscale)

Events are exported by the OpenSIPS core through the Event Interface.


1.  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:

2.  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:

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

3.  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:

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

4.  Process Auto-Scaling (upscale and downscale)

Event: E_CORE_PROC_AUTO_SCALE

This event is triggered whenever a new process is created (forked) or a process is terminated due the auto-scaling logic. In order to have this event trigger, the auto-scaling must be enabled in your configuration.

Parameters:

---

Retrieved from https://www.opensips.org/Documentation/Interface-CoreEvents-3-0
Page last modified on January 10, 2022, at 09:52 AM