Forwarded to devs Advanced Monitoring extension not working with grafana 8.0.0-1

[danami]

Username: danami

TITLE

Advanced Monitoring extension not working with grafana 8.0.0-1

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Product version: Plesk Obsidian 18.0.35.2
OS version: CentOS 8.4.2105 x86_64
Build date: 2021/05/26 11:00
Revision: 79a8872782bd03d98ca90cda78a8ba20d1369c41

PROBLEM DESCRIPTION

After upgrading to grafana 8.0 from the plesk-ext-grafana repository graphs are no longer working when clicking on the advanced monitoring extension.

STEPS TO REPRODUCE

Run yum update on the server to download the new grafana 8.0 from the plesk-ext-grafana repo.

ACTUAL RESULT

After installing grafana 8.0 graphs cannot be loaded. They just display "Metric request error"

EXPECTED RESULT

Graphs should work.

ANY ADDITIONAL INFORMATION

Downgrading grafana back to 7.5.7-1 fixes the problem:

yum downgrade grafana-7.5.7-1

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Donnerkeil]

I can confirm this bug / problem.

 

[Nextgen-Networks]

See also error messages in this older post: Forwarded to devs - Grafana extension database rights too broad and cannot load unsigned backend plugin

It's a general plesk/grafana issue - independent from OS

 

[Failure404]

"Failed to start plugin" logger=plugins.backend pluginId=grafana-simple-json-backend-datasource error="Incompatible API version with plugin. Plugin version: 1, Client versions: [2]"

 

[Sergio Manzi]

I can confirm this issue too (under Centos 7, Plesk 18.0.36)

Temporarily fixed with:

• yum downgrade grafana-7.5.7-1
• yum install yum-plugin-versionlock
• yum versionlock grafana-7*

 

[martinsjr65]

Same here with
CentOS Linux 7.9.2009 (Core)
Plesk Obsidian
Version 18.0.35 Update #2

 

[H.W.B]

Same problem here.
CentOS Linux 7.9.2009 (Core)
Plesk Obsidian
Version 18.0.35 Update #2
There was a new version of Plesk-Ext-Grafana (8.0.2-1) but after installing this, still NO DATA to display....

 

[Goose]

Same for me, issue (NO DATA) came with grafana 8.0.0 and is still present with 8.0.2

Plesk Obsidian v18.0.35_build1800210526.11 os_Debian 10.0
Debian 10.9

Metric request error
Object
status:500
statusText:""
data:Object
message:"Metric request error"
config:Object
url:"api/tsdb/query"
method:"POST"
data:Object
retry:0
headers:Object
hideFromInspector:false
message:"Metric request error"

 

[mow]

Same for me, issue (NO DATA) came with grafana 8.0.0 and is still present with 8.0.2

Plesk Obsidian v18.0.35_build1800210526.11 os_Debian 10.0
Debian 10.9

Same error here.

Version	Plesk Obsidian v18.0.35_build1800210526.11 os_Debian 9.0
OS	Debian 9.13

grafana-server complains about unavailable plugins in the syslog every 30 seconds:

Jun 15 13:32:01 servername grafana-server[20470]: t=2021-06-15T13:32:01+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=1 name="Apache & PHP-FPM memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:03 servername grafana-server[20470]: t=2021-06-15T13:32:03+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=2 name="nginx memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:06 servername grafana-server[20470]: t=2021-06-15T13:32:06+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=3 name="Mail server memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:06 servername grafana-server[20470]: t=2021-06-15T13:32:06+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=4 name="MySQL memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:12 servername grafana-server[20470]: t=2021-06-15T13:32:12+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=9 name="Swap usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:12 servername grafana-server[20470]: t=2021-06-15T13:32:12+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=5 name="Plesk memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:16 servername grafana-server[20470]: t=2021-06-15T13:32:16+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=6 name="Partition \"/\" utilization" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:17 servername grafana-server[20470]: t=2021-06-15T13:32:17+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=8 name="Real memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:19 servername grafana-server[20470]: t=2021-06-15T13:32:19+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=7 name="Partition \"/boot\" utilization" error="request handler error: plugin unavailable" changing state to=keep_state
[...]

Jun 15 13:32:31 servername grafana-server[20470]: t=2021-06-15T13:32:31+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=1 name="Apache & PHP-FPM memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:32 servername grafana-server[20470]: t=2021-06-15T13:32:32+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=6 name="Partition \"/\" utilization" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:33 servername grafana-server[20470]: t=2021-06-15T13:32:33+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=4 name="MySQL memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:33 servername grafana-server[20470]: t=2021-06-15T13:32:33+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=2 name="nginx memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:36 servername grafana-server[20470]: t=2021-06-15T13:32:36+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=3 name="Mail server memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:38 servername grafana-server[20470]: t=2021-06-15T13:32:38+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=5 name="Plesk memory usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:38 servername grafana-server[20470]: t=2021-06-15T13:32:38+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=9 name="Swap usage" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:38 servername grafana-server[20470]: t=2021-06-15T13:32:38+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=7 name="Partition \"/boot\" utilization" error="request handler error: plugin unavailable" changing state to=keep_state
Jun 15 13:32:40 servername grafana-server[20470]: t=2021-06-15T13:32:40+0200 lvl=eror msg="Alert Rule Result Error" logger=alerting.evalContext ruleId=8 name="Real memory usage" error="request handler error: plugin unavailable" changing state to=keep_state

 

[IgorG]

The bug is confirmed. We are working on EXTPLESK-2710

 

[LTUser]

Temporary fix for Ubuntu Users: (Plesk Obsidian)

sudo apt-get install -y adduser libfontconfig1
wget https://dl.grafana.com/oss/release/grafana_7.5.1_amd64.deb
sudo dpkg -i grafana_7.5.1_amd64.deb

Hth.

 

[klodoma]

Same here.

grafana-server -v
Version 8.0.2 (commit: 5c5d45e19f, branch: HEAD)

 

[Pleskie]

Any updates on this? My 'messages' log is still flooding with grafana errors every second. Just updated to grafana 8.0.3-1 using Plesk Panel. Doesn't make any difference. Flooding is still going on.

 

[Cthierry]

La mise à jour pour grafana 8.0.3 est disponible sauf qu'une fois la mise à jour terminée, la mise à jour pour grafana 8.0.3 est disponible. Il boucle et boucle et boucle.

 

[Bitpalast]

It seems that an update to Grafana 8.0.3 was available, but now that we want to install it, it's gone and the system reports that it is already up-to-date. This probably coincides with @Cthierry 's post of an infinite loop through the update process.

To remove the false update message you have to go into the system updates option of Tools & Settings and re-check for updates. The unavailable update should then be removed.

Hopefully it's just a revoked update file so that at a later time an updated Grafana version will become available again.

 

[Cthierry]

Thanks Peter, it worked and the update disappeared. Have a nice weekend.

 

[Sergio Manzi]

Still not working here with Grafana Server Version 8.0.3 (commit: cae5c5e46b, branch: HEAD) and Grafana Extension 1.2.3-233 (even though it says that EXTPLESK-2710 is solved), and again downgrading to grafana-7.5.7-1 makes things work.

As above, I'm working under CentOS Linux 7.9.2009, Plesk 18.0.36

====

I'm quite concerned by what Grafana Extension change log states:

"To use the upcoming Advanced Monitoring version 1.4.3 with Grafana 8.0, you need to have the latest version of the Grafana extension."

What does that exactly means? Isn't "Advanced Monitoring" the very same thing that "Grafana Extension"? What am I missing?

Forget it! Just a brain fa*t from my part... :-/

 

[H.W.B]

Also here still not working with Grafana 8.0.3

 

[UHolthausen]

Hello

since this afternoon the extension is working again.
Check the updates
Advanced monitoring should be 1.4.3-298
Grafana extension 1.2.3-233
grafana server 8.0.3

 

[Sergio Manzi]

since this afternoon the extension is working again.

Yup! Same here!

Upgrading "Advanced Monitoring" (and then Grafana Server to 8.0.3) did the trick, beside a minor hickup about some json not being installed, fixed by the ad-hoc "Fix installation" button.

... but I'm quite positive that the Advanced Monitoring extension upgrade wasn't offered this morning (European time): am I wrong?