• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Clicking on "Use Built-in Monitoring" does not work

Mato

New Pleskian
Username:

TITLE

Clicking on "Use Built-in Monitoring" does not work

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.63_build1800240902.09 / Debian 11.11 / Xeon E3-1230 v6

PROBLEM DESCRIPTION

In the Monitoring page, clicking on the button "Use Built-in Monitoring" gets a "Request aborted" in the upper right corner and simply reloads the page.

I hoped that Grafana would be back to normal after disabling 360 Monitoring and clicking this button.

STEPS TO REPRODUCE

  1. Grafana is installed and working.
  2. Follow procedure to install 360 monitor :
    1. Connect server to Plesk (login)
    2. Activate 360 Monitoring (installs agent on server)
  3. Try to go back to Grafana (because there is no Android app for Plesk 360)
    1. In the 3-dotted menu, click on "Go back to built-in monitoring"
    2. red notification in the upper-right corner says "Request aborted"
  4. Try again, this time with the official script :
    1. Find the thread where you remove the agent360 from server : Uninstalling 360 Monitoring
    2. execute the automatic uninstall -> it works well
  5. Now there is a button saying "Use Built-in Monitoring" to get back to Grafana, but clicking on it still displays "Aborted request" and does nothing but reloading the page.

ACTUAL RESULT

"Use Built-in Monitoring" button does not work.

EXPECTED RESULT

Grafana should be back after clicking the button "Use Built-in monitoring".

ANY ADDITIONAL INFORMATION

It seems strange that the button sends a DELETE request when clicked :
DELETE /modules/monitoring/index.php/cloud-statistics/toggle-monitoring-view undefined

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
Thank you for the report. Unfortunately, I was unable to reproduce the issue on a Debian 11 test server with Plesk 18.0.63. With that said, the issue is most likely due to the specific configuration of the server itself. Therefore, I would suggest opening a ticket with Plesk support for an investigation of the issue on your server. To sign-in to support and open a ticket go to:
If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative to get support directly from Plesk:
 
Hi,
the only specific parameters are for the NGinx and are very straightforward :
proxy_buffers 8 16k;
proxy_buffer_size 32k;
fastcgi_buffers 8 16k;
fastcgi_buffer_size 32k;
There are no big extension, as it is only a simple webservice server.
The problem is with the Grafana extension, which has been disabled by Monitor360, and can't be enabled again..

Maybe you could try and switch between Monitoring360 and Grafana a few times? I am sure there is definitely a problem here.

I will try to remove and reinstall the Grafana extension and comme back with my result.
 
  1. I removed the Grafana extension in the Extension panel.
  2. Then I clicked on the "Use the built-in monitoring" button. This time, there was a response, as the small icon started to turn.
  3. after a few seconds, the page reloaded, but stayed the same : the button was still here and Grafana was not back.
  4. And a click on the button had the same result as before : "Request aborted".
  5. Coming bak to the extensions, I can see that Grafana has been reinstalled, but is still not displayed when clicked on "Open".
 
Hey, @Mato. Regardless of what I tried:

  1. Installing the Grafana extension manually before enabling it in Monitoring > enabling built-in-monitoring > switching to 360 monitoring > switching back to in-build-monitoring > switching back to 360 Monitoring
  2. Directly enabling Built-in-monitoring > switching to 360 monitoring > switching back without uninstalling 360 / switching back leaving 360 installed
I am unable to reproduce the issue.

If you do not have option to open a support ticket, could you please check /var/log/plesk/panel.log for any Monitoring/Grafana-related errors?
 
Hi,
thank you for your interest but I think the problem is now solved.
I did :
grep -i 'grafana' /var/log/plesk/panel.log
but it returned empty.

Interestingly, the 2 last strings of the file were :
[2024-10-18 06:30:04.559] 4038138:6711e44c84d8b ERR [panel] PleskExt\Monitoring\CloudApi\Monitoring360\Monitoring360ApiBroker::getLicenseInfo(): Argument #1 ($userId) must be of type string, null given, called in /opt/psa/admin/plib/modules/monitoring/library/StatisticsCollector.php on line 69
[2024-10-18 14:02:13.703] 4060016:67124e45abbcf ERR [extension/monitoring] /opt/psa/admin/plib/modules/monitoring/library/Http/HttpClient.php(14): PleskExt\Monitoring\Http\HttpClient::__construct(): Argument #1 ($baseUrl) must be of type string, null given, called in /opt/psa/admin/plib/modules/monitoring/library/CloudApi/Monitoring360/Monitoring360ApiClient.php on line 24

Which showed Monitoring360 was still running and crashing somehow.

So I uninstalled the Grafana extension, but also the Monitoring extension.
After re-installing Monitoring, the "Use Built-in Monitoring" was not the same, with a better/newer UX.
Clicking it reinstalled Grafana, which is now displayed properly.

So the culprit was the Monitoring extension, which needed uninstalling and reinstalling.

Thanks for your help, as you pointed me to logs, where the solution was. (As always?)

Regards,
 
Back
Top