Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility of PRTG Datasource with upcoming Grafana v11.0? #206

Open
Di0g00 opened this issue Apr 23, 2024 · 6 comments
Open

Compatibility of PRTG Datasource with upcoming Grafana v11.0? #206

Di0g00 opened this issue Apr 23, 2024 · 6 comments

Comments

@Di0g00
Copy link

Di0g00 commented Apr 23, 2024

In pre-relase notes for Grafana 10, it is stated that support for Angular is turned off by default. Hence any plugin not migrated away from Angular will fail to work.

Angular is deprecated and turned off by default for new Grafana Cloud stacks

You are affected if:
You create a new Grafana Cloud stack and intend to use any panel or data source plugins written using the Angular.js JavaScript framework. See the list of Angular plugins.

Background
AngularJS is an old frontend framework that stopped active development many years ago. Because of that, it’s a security risk. AngularJS also requires unsafe-eval in the CSP (Content Security Policy) settings, which also reduces the security level of how javascript is executed in the browser.

Angular plugin support in Grafana is deprecated, meaning it will be removed in a future release. There are still some community and private plugins built using Angular. Starting with v9.0, Grafana has a server configuration option, called angular_support_enabled, that controls whether Angular plugin support is available.

Change in Grafana v10
Angular is disabled by default for all new Grafana Cloud stacks. Existing stacks in Grafana Cloud, Grafana Enterprise on-premise instances, and Grafana OSS instances will not be automatically impacted.

Are there any plans to move PRTG datasource from Angular framework ? Thanks in advance!

@angela-d
Copy link

He posted a while ago he's no longer working with PRTG so there's no incentive to update it.

If someone doesn't want to fork the plugin, there's other options like changing the data sources.
I've been slowly migrating my most important content to RSS feeds that hook into PRTG's API. Once I have something suitable for sharing, I'll post it to Github.

@DCaccu
Copy link

DCaccu commented Apr 25, 2024

He posted a while ago he's no longer working with PRTG so there's no incentive to update it.

If someone doesn't want to fork the plugin, there's other options like changing the data sources. I've been slowly migrating my most important content to RSS feeds that hook into PRTG's API. Once I have something suitable for sharing, I'll post it to Github.

That would be very helpful for us since we are worried about how to do this. Thanks for the help.

@digdilem
Copy link

Did any workable solution arrive for PRTG?

Just tried to upgrade Grafana and of course it disabled the Angular plugin for PRTG.

@JavierCCC
Copy link

Same situation here. If i have to decide to leave a product, that product will not be grafana.

@digdilem
Copy link

It is very disappointing that Paessler didn't step in and provide a working plugin for grafana.

They've just increased our annual fee from £1600 to £6100 for PRTG, despite not having really changed anything for years. So that and this means we're moving to Zabbix. Which is free and has a perfect working plugin for Grafana.

PRTG looks to be going the same way as vmware. We're not the only people moving away.

@Di0g00
Copy link
Author

Di0g00 commented Oct 9, 2024

Good morning,
Do you already have any news regarding Plugin migration?
Thanks in advance

@Di0g00 Di0g00 changed the title Compatibility of PRTG Datasource with upcoming Grafana v11.0 ? Compatibility of PRTG Datasource with upcoming Grafana v11.0? Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants