From checkmk-werks-lvl1@lists.checkmk.com Tue Jul 9 12:48:48 2024 From: Checkmk werks level 1 To: checkmk-werks-lvl1@lists.checkmk.com Subject: [2.3.0] Checkmk Werk 15244 adapted: New agent configuration: Push mode Date: Tue, 09 Jul 2024 12:48:46 +0000 Message-ID: <1720529326.392323.470.nullmailer@localhost> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6274001512444978013==" --===============6274001512444978013== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Werk 15244 was adapted. The following is the new Werk, a diff is shown at the= end of the message. Title: New agent configuration: Push mode Class: feature Compatible: compat Component: agents Date: 1678199258 Edition: cce Knowledge: undoc Level: 2 Version: 2.3.0b1 Users of the Checkmk Cloud Edition now have a new mode of operation for the a= gent controller at their disposal: The "Push mode". In the push mode, the Checkmk agent sends the monitoring data to the Checkmk = server once per minute. The agent pushes the data transmission on its own and does not wait for a req= uest from the server. The push mode is always required if the Checkmk server cannot access the netw= ork in which the host to be monitored and its agent are located, for example,= in a cloud-based configuration. More on the setup can be found in our user manual. -----------------------------------------------------------------------= -------- Title: New agent configuration: Push mode Class: feature Compatible: compat Component: agents Date: 1678199258 - Edition: cre ? ^ + Edition: cce ? ^ Knowledge: undoc Level: 2 Version: 2.3.0b1 =20 Users of the Checkmk Cloud Edition now have a new mode of operation for the= agent controller at their disposal: The "Push mode". =20 In the push mode, the Checkmk agent sends the monitoring data to the Checkm= k server once per minute. The agent pushes the data transmission on its own and does not wait for a r= equest from the server. The push mode is always required if the Checkmk server cannot access the ne= twork in which the host to be monitored and its agent are located, for exampl= e, in a cloud-based configuration. =20 More on the setup can be found in our user manual. =20 --===============6274001512444978013==--