trailpolt.blogg.se - Plesk php 8.1

litespeed - enable or disable data import from LiteSpeed, default is auto (autodetect) On| on| 1 - force use litespeed Off| off| 0 - force use apache.max_snapshots_per_incident - the maximum number of snapshots saved for one "incident".snapshots_per_minute - the maximum number of snapshots saved per minute for specific LVE id (default is 2).

If minimal interval of time between LVE faults is greater than value specified, than new "incident" will begin and new snapshots will be saved. period_between_incidents - the minimal interval of time between incidents (in seconds).etc/sysconfig/nfig/SnapshotSaver.cfg contains the following options: Possible values:Ĭonfiguration files for plugins are located in /etc/sysconfig/nfig directory. You should recreate lvestats database by command lve-create-db -recreate if you change the option's value from false to true. Top border is the biggest value which kmodlve can use as LVE ID. It allows using the user uids more than 10 9 and up to 2 31-2 (2 147 483 646). Use_big_uids - the option is available from lvestats version 3.0.14-1. Hide_lve_more_than_maxuid - disable displaying of lve ids more than max uid in resource usage. When mode parameter is absent, later version of lveinfo is implied.ĭisable_snapshots - disable snapshots and incidents. Support of v2 mode will be added to LVE plugins in the recent future. Value v2 enables extended output mode, but can break LVE plugins for control panels (statistics in LVE Manager, Resource Usage, etc).Value v1 enables compatibility with old version of lveinfo.Mode – sets compatibility output mode (compatibility with older lveinfo version Old data is removed from database automatically. Keep_history_days - period of time (in days) to keep history in database. Increasing this parameter makes precision of statistics worse. This should be less than total duration of execution of all plugins. Interval - duration of one cycle of lvestats-server (seconds). If plugin execution does not finish within this period, plugin is terminated. Timeout - timeout for custom plugins (seconds). Plugins – path to directory containing custom plugins for lve-stats (default path /usr/share/lve-stats/plugins).ĭb_timeout - period of time to write data to database (in seconds) default value is 60 seconds. For use with sqlite database, value of this option should be "localhost" (without quotes). This option is to use with centralized database ( PostGreSQL or MySQL). Server_id - sets the name of the server (at most 10 characters). Connection string is not used for sqlite database.

more pretty, scalable, interactive charts ĭefault port is used for specific database, if port is not specified (typical port is 3306 for MySQL and 5432 for PostGreSQL).implemented ability to add custom plugins.

improved notifications about hitting LVE limits (more informative and without false positives).

lvestats-server saves “snapshots” of user’s processes and queries for each “incident” - added new lve-read-snapshot utility.

lvestats-server emulates and tracks faults for CPU, IO, IOPS.

CPU usage is calculated in terms of % of a single core (100% usage means one core).

Old LVE-statistics functionality is hard to extend.

Notifications in old LVE-statistics are not accurate because they are based on average values for CPU, IO, IOPS.

what processes are running when user hits LVE limits.Example

Old LVE-statistics does not provide a way to determine a cause of LVE faults, i.e.

On 32 core servers usage is not visible for most users (as they are limited to 1 core).

100% CPU usage in old lve statistics means “all cores”.

So, such peak load will noExat be recorded and we need to store data with much higher precision. Data in old LVE-statistics is aggregated to 1-hour intervals. If user used 100% of CPU for 1 second within an hour, it is only 1-2% for a minute, and 0 for 5 minutes.

Old LVE-statistics store averages as integer numbers, as % of CPU usage.

What features will be implemented in the future?.

# General information and requirements # LVE-Stats 2 # General information and requirements