From MAILER-DAEMON Sun Jan 15 21:38:07 2023 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1pHFNv-0003on-7i for mharc-monit-general@gnu.org; Sun, 15 Jan 2023 21:38:07 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pHFNu-0003ob-3U for monit-general@nongnu.org; Sun, 15 Jan 2023 21:38:06 -0500 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pHFNs-0007Lr-78 for monit-general@nongnu.org; Sun, 15 Jan 2023 21:38:05 -0500 Received: by mail-lj1-x229.google.com with SMTP id e16so1787343ljn.3 for ; Sun, 15 Jan 2023 18:38:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ackcio-com.20210112.gappssmtp.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Cv1c31llL+b4YTqcVZ78Z7vxov4o/6BseR+Pxixgcf4=; b=nBbz99l3DAh2f5iuGgQsUmbwv5zviO4vnIp8Gajw6nl7x0FKMQTCSBtsCwE0kB1tes L3sTT8xjVbgrvuMIVXBaDIFHgCiZqU0U3Na82nbCQKvrA7PvJ6oFWf9RbwqAHUS0+KV6 O1EMyRSbpVBlWG/zWpd3P0XrbkVZWYRgL7eS6r+8Ynp0+ckHT+in7TFfLNxEVLArBbv4 Cv5htPEvTcOXbAFjsVxI/H8z+NwH6Kt/1rPYUE88CQoUGBmSVomRrtjpQ37yYvXRfx/7 wBznHrf8IMnNNABSrdbNqvAQQP0o0rgkPKxs9ouNuAReaH8ea0aLkinkYnQzzafD+sHc ED7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Cv1c31llL+b4YTqcVZ78Z7vxov4o/6BseR+Pxixgcf4=; b=7GMfa60VTqMNNShfZjzynyTSVlKBrE7DfSPCmc+FwyQnLJ2f7UNS3YMvMkDn8g+PG2 xM3Dpdg9rfIKX9FUZSeBDuGHdec6Y9cIRC3kiVA6eUO/Sa2DCOXg3HSKZbDmJqeE6rJj cT3yECqmgldiLAYvZBavnvgYy3MT0903AhxZKPKD56blnaRd+E0ghAGlnKYA1P0wtFkz nrGzIqIxpfoYbOM5/fjNiPrf6hJFPDKg66i+wQ8I1thSUBIt1nc0/EVeB8Lr4pBTaqvW /BpXOMbjScdzJIWDiEbaoksotBaXnjrpgh0IOAahVlcStWDhZJWC0PsNujpR+SJwabta I7Sg== X-Gm-Message-State: AFqh2kpLqsD9hV7IsRvTmD950BCQCXFKCq2CCbjiLAtVOSbxQTsca7YI CgJJI0b5Y4fiygC9BzxVI3vpSU+zqM1+5Qt/owAlo7VuWkC8gxaI X-Google-Smtp-Source: AMrXdXsMaUtmiFkS2On+tuyD/178KX4VvXzj/YIL8kug9k8xRNDzbVjkMC1y+dXp6n8+z5JAE+5T4PwVBgrD5EHbIZA= X-Received: by 2002:a05:651c:17a3:b0:27f:cae7:c1d8 with SMTP id bn35-20020a05651c17a300b0027fcae7c1d8mr3538661ljb.388.1673836680989; Sun, 15 Jan 2023 18:38:00 -0800 (PST) MIME-Version: 1.0 From: Leonard Teng Date: Mon, 16 Jan 2023 10:37:51 +0800 Message-ID: Subject: Monit load average monitoring To: This is the general mailing list for monit Content-Type: multipart/alternative; boundary="000000000000c869a505f25878ac" Received-SPF: pass client-ip=2a00:1450:4864:20::229; envelope-from=leonard@ackcio.com; helo=mail-lj1-x229.google.com X-Spam_score_int: 0 X-Spam_score: 0.0 X-Spam_bar: / X-Spam_report: (0.0 / 5.0 requ) BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: monit-general@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: This is the general mailing list for monit List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2023 02:38:06 -0000 --000000000000c869a505f25878ac Content-Type: text/plain; charset="UTF-8" Hi all, Just wanted to inquire about the load average monitoring option on Monit. From the manual, it states the following: The load average is the number of processes in the system run queue per CPU core, averaged over the specified time period. Could I get some clarity on how this system run queue works, and how does this compare to the other CPU utilization option? Additionally, what would be good values to configure for this load average value? Regards, Leonard --000000000000c869a505f25878ac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Just wante= d to inquire about the load average monitoring option on Monit. From the ma= nual, it states the=C2=A0following:

The load average is t= he number of processes in the system run queue per CPU core, averaged over = the specified time period.

Could I get = some clarity on how this system run queue=C2=A0works, and how does this com= pare to the=C2=A0other CPU utilization option? Additionally, what would be = good values to configure for this load average value?=C2=A0

<= /div>
Regards,

Leonard
--000000000000c869a505f25878ac-- From MAILER-DAEMON Mon Jan 16 03:28:37 2023 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1pHKr6-000479-UN for mharc-monit-general@gnu.org; Mon, 16 Jan 2023 03:28:37 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pHKr5-00046p-72 for monit-general@nongnu.org; Mon, 16 Jan 2023 03:28:35 -0500 Received: from mail.interpool.de ([185.250.248.246]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pHKr3-0001BW-AH for monit-general@nongnu.org; Mon, 16 Jan 2023 03:28:34 -0500 Received: by mail.interpool.de (Postfix, from userid 337) id D8699102474; Mon, 16 Jan 2023 09:28:27 +0100 (CET) Received: from smtpclient.apple (pd9ebf6a6.dip0.t-ipconnect.de [217.235.246.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.interpool.de (Postfix) with ESMTPS id 75B4510137C for ; Mon, 16 Jan 2023 09:28:27 +0100 (CET) From: Tino Hendricks Content-Type: multipart/alternative; boundary="Apple-Mail=_0596AF8B-CD8C-4178-94C6-701F21855D8F" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: Monit load average monitoring Date: Mon, 16 Jan 2023 09:28:27 +0100 References: To: This is the general mailing list for monit In-Reply-To: Message-Id: <25E51E8C-E46B-4DED-B96A-3DDC25AEE22C@interpool.de> X-Mailer: Apple Mail (2.3696.120.41.1.1) Received-SPF: pass client-ip=185.250.248.246; envelope-from=t.hendricks@interpool.de; helo=mail.interpool.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: monit-general@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: This is the general mailing list for monit List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jan 2023 08:28:35 -0000 --Apple-Mail=_0596AF8B-CD8C-4178-94C6-701F21855D8F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Leonhard, I think this is not a monit specific question or at least can=E2=80=99t = be easily answered. As for the calculation for CPU utilization there are tons of = explanations on the web, i.e. https://community.tenable.com/s/article/What-is-CPU-Load-Average = And that makes clear that =E2=80=9Egood values=E2=80=9C are hard to give = because it very much depends on your setup.=20 Our main office server is very much bored around 0.05 since most = services went to the cloud. Wikimedia servers are used to +50% all the time. = https://grafana.wikimedia.org/d/000000377/host-overview?orgId=3D1&var-serv= er=3Dalert1001&var-datasource=3Dthanos&var-cluster=3Dalerting = I would start with aggressive ( =3D low) values and if you get too many = false positives adjust them up. Best, Tino > Am 16.01.2023 um 03:37 schrieb Leonard Teng : >=20 > Hi all, >=20 > Just wanted to inquire about the load average monitoring = option on Monit. =46rom the manual, it states the following: >=20 > The load average is the number of processes in the system run queue = per CPU core, averaged over the specified time period. >=20 > Could I get some clarity on how this system run queue works, and how = does this compare to the other CPU utilization option? Additionally, = what would be good values to configure for this load average value?=20 >=20 > Regards, >=20 > Leonard --Apple-Mail=_0596AF8B-CD8C-4178-94C6-701F21855D8F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = Leonhard,

I think = this is not a monit specific question or at least can=E2=80=99t be = easily answered.

As for the calculation for CPU utilization there are tons of = explanations on the web, i.e.

And that = makes clear that =E2=80=9Egood values=E2=80=9C are hard to give because = it very much depends on your setup. 
Our main = office server is very much bored around 0.05 since most services went to = the cloud.
Wikimedia servers are used to +50% all = the time.

I = would start with aggressive ( =3D low) values and if you get too many = false positives adjust them up.

Best,

Tino

Am = 16.01.2023 um 03:37 schrieb Leonard Teng <leonard@ackcio.com>:

Hi all,

  =       Just wanted to inquire about the load average = monitoring option on Monit. =46rom the manual, it states = the following:

The = load average is the number of processes in the system run queue per CPU = core, averaged over the specified time period.

Could I get some clarity on how = this system run queue works, and how does this compare to = the other CPU utilization option? Additionally, what would be good = values to configure for this load average value? 

Regards,

Leonard

= --Apple-Mail=_0596AF8B-CD8C-4178-94C6-701F21855D8F--