5 results found
-
Allow single channel data to be collected from /api/historicdata.json endpoint
If a sensor has multiple channels it is very desirable to be able to collect the data for a single channel fron this endpoint.
For example:
http://xyz-prt/api/historicdata.json?id=123&channelid=19&avg=0&sdate=2026-02-01-00-00-00&edate=2026-02-10-02-59-59Currently only a single channel is returned and there doesn't seem to be any control over which channel that is.
1 voteHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. Reason:
- API v2 already has more flexibility to define specific channels when returning the precalculated data sets (e.g. live, 2 days, 30 days...)
- API v2 will support the same flexibility once granular historic data retrieval is supported
- We will not invest in change the functionality of API v2 which is referenced here.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
Enable Direct Database Access in PRTG for Enhanced Third-Party Integration
As an IT Infrastructure Manager, I want access to PRTG's underlying database so that I can directly integrate our monitoring data with external analytics or visualization tools such as Grafana or custom Python / PowerShell scripts, to create unified dashboards across multiple data sources, and build custom analytics without relying on intermediate export tools or API polling limitations
Currently, integrating PRTG data with Grafana requires intermediate tools such as the PRTG Data Exporter or API bridges, which adds extra complexity, performance overhead, and maintenance effort. PRTG should have an optional direct connection interface to its database for read-only access under…
1 voteHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
The use of the PRTG database will be gated by the API v2. The reason for this is that the future database is using additional components on top of our SQL+time series database making queries more complex for the typical user.
We are working on a new Grafana plugin which uses the new API v2, but in order to scale and consolidate multiple PRTG servers you will still need the data exporter extension for the time being.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
Native Integration with ITSM Platforms for MSPs
As an MSP, I want PRTG to provide native, bidirectional integrations with leading ITSM platforms (ServiceNow, Jira Service Management, Freshservice, Zendesk, BMC Helix), so that I can automatically create, update, and synchronize incidents without relying on emails and custom scripts.
Email-based notifications are outdated, and relying on complex scripts or API configurations is not practical for large-scale managed service operations.
When alerts fail to create tickets, client trust is lost immediately.
These integrations should automatically create and update incidents, synchronize device and asset data, and allow status updates to flow both ways without manual intervention.
A user-friendly interface to manage…5 votesHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time.
Please note that it will not be possible to provide full integration between PRTG and all the mentioned ITSM platforms. However, we do plan to rebuild our notifications system, and some aspects of your suggestion will be taken into account.
While we won't be able to implement your complete feature request as outlined, please don't let this discourage you from sharing your ideas with us. Your continued feedback and ideas are essential to our product evolution.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
IPam And/or Claroty Integration
We are starting now to implement core server with 10000, 16000 and 24000 sensors, and the autodiscovery is often not possible, because of very old HW & SW.
This means that we need to manually enter the whole OT device part into PRTG.
A IPAM integration would be very helpful, also for verification of the devices.1 voteHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
Allow reporting in PowerBI
We use PowerBI for a number of reporting items as well as on a "dashboard" screen - it would be helpful if we could report on PRTG data within this
1 voteHi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
- Don't see your idea?