Mem-group = "runtime": "dialog" "usrloc" "tm"įor the above example the generated statistics will be named: shmem_group_interest:fragments, shmem_group_interest:memory_used, shmem_group_interest:real_used. In order for the feature to work you have to run "make generate-mem-stats" and complile with the variable SHM_EXTRA_STATS defined. This is useful if you want to monitor the memory usage of a certain module (or group of modules). OpenSIPS will provide per-group memory information - the number of allocated fragments, the amount of used memory and the amount of real used memory (with memory manager overhead). It accepts integer values between 0 and 100.ĭefines a group of modules (by name) to get separate memory statistics.
#XLOG CENTER FREE#
Set to true in order to enable the assert script statement.Ī number representing the percentage threshold above which the E_CORE_PKG_THRESHOLD event is raised, warning about low amount of free private memory.
# filter out requests going to ips of my gwsĭst_blacklist = gw: If not defined, OpenSIPS will never down scale, but only up scale.Ĭheck if the address in top most via of replies is local. The down scaling part of the profile is optional. A process will be terminated when the overall load of the group will be lower than 20% during 10 cycles. A cycle is a time unit used for monitoring (like 2 seconds).Īlso the profile will allow the group to scale down to a minimum of 2 processes. A new process will be forked when the overall load of the group will be higher than 70% for more than 4 cycles during a 5 cycles monitoring window. This profile will allow the group to fork up to 6 processes. Scale up to 6 on 70% for 4 cycles within 5 These profiles may be used for the UDP processes (see udp_workers or socket options), TCP processes (see tcp_workers option) or TIMER processes (see timer_workers option).įor more, see this external description of auto-scaling. Also see auto_scaling_profile for more details on how the auto-scaling works.Īuto_scaling_cycle=3 # do auto-scaling checks once every 3 secondsĭefines the behavior of the auto-scaling support, in terms of how many processes should be allowed and when to terminate or create new processes. The number of seconds defining a auto-scaling cycle - the auto-scaling engine, at each cycle, is evaluating the internal load of the groups and decided if more processes needs to be created or if existing processes need to be terminated. The auto discovered aliases are result of the DNS lookup (if the 'socket' definition has a name and not IP) or of a reverse DNS lookup on the socket IP.įar backward compatibility reasons, the default value is "off"/0. This parameter controls if aliases should be automatically discovered and added during fixing listening sockets. It is necessary to include the port (the port value used in the "socket=" definitions) in the alias definition otherwise the loose_route() function will not work as expected for local forwards! If the ":port" part is omitted, all ports of the given "hostname" will be considered an alias (similar behavior to port 0). It can be set many times, each value being added in a list to match the hostname when 'myself' is checked. Parameter to set alias hostnames for the server. Same warnings as for 'advertised_address'. If empty or not set (default value) the port from where the message will be sent is used. The port advertised in Via header and other destination lumps (e.g. When advertise values are defined per interface, they will be used only for traffic leaving that interface only. NOTE: Aside this global approach, you can also define an advertise IP and port in a per-interface manner (see the socket parameter).
you can set anything here, no check is made (e.g. don't set it unless you know what you are doing (e.g. If empty or not set (default value) the socketĪddress from where the request will be sent is used. It can be an IP address or string and represents the address advertised in Via header and Set to true in order to make OpenSIPS shut down immediately in case a script assert fails. If you need to specify either "yes" or "no" as part of a string, wrap this in double quotes. Accepted values are, depending on the actual parameters strings, numbers and yes/ no. Global parameters that can be set in configuration file. This section lists the all the parameters exported by OpenSIPS core for script usage (to be used in opensips.cfg). 1.69 tcp_listen_backlog (Replaced in OpenSIPS 3.1).
0 kommentar(er)
