• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue [EXTPLESK-4022] Plesk Monitoring - Saving Thresholds throws error

gbotica

Regular Pleskian
Server operating system version
AlmaLinux 8.6
Plesk version and microupdate number
Version 18.0.47
Hi,
I have 3 Plesk servers running AlmaLinux and 1 running Ubuntu 20.04 and all with Plesk 18.0.x.

All have the latest version of the Monitoring and Grafana extensions
Grafana Version: 1.3.4-292
Monitoring Version: 2.5.0-744

I've just discovered that saving Thresholds is broken and Plesk shows an error: "Request failed with status code 500" and no changes to Thresholds are saved. This issue occurs on all 4 servers. This means we cannot make any changes to the current thresholds and alert notifications in Plesk.

I've checked /var/log/grafana/grafana.log - but there's nothing there.

I note that there is a newer Alert system in Grafana 8+. On the Grafana Alerting -> Alert Rules page there is a message: "You are using the legacy Grafana alerting."

So maybe the current Plesk integration is broken?

Is this a known issue? Anyone else have this problem?

1666649437610.png

1666649102152.png
 
I have the same issue on all 4 my servers. i cannot change the threshold on any of them.
Ubuntu 18 Plesk Version 18.0.47 Update #5
+
Ubuntu 20 Plesk Version 18.0.47 Update #5
 
This look like a bug. Can one of you please submit a report?

 
Hi everyone,

It is known bug (EXTPLESK-4022) and it is on the fixing stage now, the fix will be available with the next bug-fix release.
 
Hi everyone,

The new version of the Plesk Monitoring is released.

2.5.1 (28 October 2022)​

  • [-] It is no longer possible to bypass the "cloudMaxWebsites" limit via the CLI. (EXTPLESK-4031)
  • [-] It is again possible to save thresholds. (EXTPLESK-4022)
 
Back
Top