Resolved Wrong cpu subscription monitoring

[ivanes82]

For about a week in subscription cpu usage it gives percentages that don't make any sense.
Centos 7 - I have tried to format and install the os and plesk and it still happens. Was something broken in the last update?

 

[Cris987]

Same problem here. A week ago I ran the Plesk update and now the subscriptions went from showing 24% to 24000% usage.

Ubuntu 20

 

[franco68]

Having the same problem on
Ubuntu 20.04.4 LTS
Product
Plesk Obsidian
Versie 18.0.41 Update #1

 

[Bitpalast]

Important - PLEASE FOLLOW THIS INSTRUCTION IF YOU BELIEVE THAT FOUND A BUG!

Dear Pleskians, Please, click Submit Report button and use the template in this special forum subsection if you really believe you discovered a new bug and need to report it to the Plesk developers. It does allow us to handle and resolve your requests much more efficiently. Please be careful...

talk.plesk.com

 

[franco68]

Important - PLEASE FOLLOW THIS INSTRUCTION IF YOU BELIEVE THAT FOUND A BUG!

Dear Pleskians, Please, click Submit Report button and use the template in this special forum subsection if you really believe you discovered a new bug and need to report it to the Plesk developers. It does allow us to handle and resolve your requests much more efficiently. Please be careful...

talk.plesk.com

None of the current reporters is allowed to file an official report. So someone else has to do that?

 

[Cris987]

Today Grafana was updated to version 1.3.2. Unfortunately it does not solve the problem mentioned here.

 

[franco68]

After update:

Forwarded to devs - No graphs in monitoring after grafana-8.3.6-1.x86_64 update

Username: TITLE No graphs in monitoring after grafana-8.3.6-1.x86_64 update PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS Linux 7.9.2009 (Core) Plesk Obsidian Version 18.0.41 Update #1 PROBLEM DESCRIPTION After the grafana-8.3.6-1.x86_64 update, the graphs don't work...

talk.plesk.com

 

[ivanes82]

This error is still present.

 

[Cris987]

After the latest update of the Monitoring extension to version 2.3.2-675 the problem seems to be solved.

 

[ivanes82]

Solved, Thank you !!!