Keep up-to-date with the latest release notes from the PRTG Data Exporter, a PRTG product extension.
For more information about PRTG Data Exporter, see the PRTG Data Exporter manual.
November 10, 2026 - PRTG Data Exporter 2026.11.7.1050
Important
In order to update to this version, pay special attention to the following:
Worker agent permissions
If you run worker agents that were set up with an earlier version, update in this order:
Update the manager. This creates the new tables in the configuration database.
Run the updated agent setup SQL script on the configuration database.
Update the worker agents.
Without the script, data collection on those agents fails with a database permission error, and their logs don’t show up on the agent dashboard.
Grafana dashboards
Existing Grafana dashboards are not updated automatically, and deploying a dashboard again does not replace the existing one. After the update, delete any deployed dashboards and deploy them again from the Data Exporter UI. The new dashboards get new URLs, so update any bookmarks or links to them.
All dashboards need this to show times in your Grafana timezone and to show the new Stale and Paused statuses in their Data Collection Status panel.
Business Process - Overview and Business Process - Components also show Paused and Stale for business processes whose status data profile has stopped collecting.
Geo Map - Site Status and Geo Map - Connectivity are new. Deploy them from the Data Exporter UI.
- If you have customized a dashboard, keep it and create the new version in a temporary folder in Grafana. Copy the updated panels into your customized dashboard, set its time zone to Default in the dashboard settings, and then delete the temporary folder.
Features
We added two new Grafana dashboards, Geo Map - Site Status and Geo Map - Connectivity, that show your sites, devices and groups on a map with their status, latency, bandwidth and site health, based on the GPS coordinates in the PRTG Location field. You can also show links per site, for example to camera feeds or runbooks, by adding them to the PRTG Comments field in this JSON format: {"pde":{"geomaps":{"metadata":[{"type":"link","value":"https://..."}]}}}. A plain URL in the Comments field is not picked up.
We added per-agent addresses for target databases. You can now set a host and port for each worker agent, for example when an agent reaches the database through a proxy, while Grafana and agents without their own address keep using the database’s central address. You manage these addresses in the target database dialog and the agent setup wizard. A failed collection now names the address that was used, in the logs and in the profile History tab.
We added a connection test per agent. The Target Database screen lists every active agent with the address it connects through and lets you test the connection from that agent. A failed test explains why, for example not reachable, no address configured or agent offline.
We added central agent logs. You can browse an agent’s log entries on the agent dashboard and filter them by level and date range. Old entries are deleted after 7 days by default, and you can change this period.
We added the Stale and Paused statuses. Profiles that stop collecting are shown as Stale in the Data Exporter and in Grafana, and profiles stopped on purpose are shown as Paused. Business processes also show Paused or Stale when their status data profile has stopped collecting, instead of keeping their last status.
We added a notifications bell to the top right of the top bar. It lists profiles whose last run failed or finished with warnings, and updates automatically after the next successful run.
Changes
We now confirm the start of a data collection at once: the profile shows Starting and then Running. A start is refused when a run of the profile is already queued or running, or when its agent is offline.
We now show an agent that stops responding as Offline faster, and an agent that comes back is online again within about a minute.
We simplified how you enter a PRTG server address: the separate Protocol and Port fields are replaced by a single URL field, for example https://your-server:port.
We added support for Microsoft SQL Server 2025.
We made the License Information page open faster. It keeps showing the number of used PRTG servers when a license check times out, and a successful license check is no longer reported as a timeout.
We made license key changes take effect without restarting the services.
We made data collection to PostgreSQL target databases more reliable through slow proxy chains: connections are reused, and a connection that hangs while opening is retried.
We made log detail messages selectable in the history view, so you can now easily highlight and copy text to paste into support tickets or search engines.
We improved PostgreSQL connection handling in multi-agent deployments, so several agents starting at the same time, for example after an update, no longer run into connection limit errors. The configured worker count is now respected.
We now digitally sign all Data Exporter executables and installers. Windows now shows Paessler as the verified publisher instead of “Unknown publisher”, which reduces security warnings during installation.
We sorted the schedule selection dropdown by duration instead of alphabetically, so shorter intervals appear at the top and longer ones at the bottom, making it easier to find the right schedule at a glance.
We improved tag-based saved filters. When reopening a saved filter configured with tags, objects now accurately show only the count of sensors matching the selected tags (instead of the total sensor count). In addition, warnings for invalid selections are now properly displayed.
We made updates with large PostgreSQL target databases more reliable. After the update, the channel value table is converted in batches in the background, so the migration no longer times out. While the conversion runs, data collection for the profiles that write to that database is paused. It resumes automatically when the conversion is done.
Bugfixes
We fixed an issue where agents that went Offline and came back did not get their scheduled jobs back until their services were restarted.
We fixed an issue where deleted profiles continued to appear in the Grafana Data Collection Status with their last result. Deleted profiles are now removed automatically.
We fixed an issue where Grafana dashboards always displayed times in UTC regardless of user timezone settings. Newly created dashboards now use Grafana’s default timezone, respecting your profile or browser settings (to apply this to existing dashboards, delete them and deploy them again as described in the upgrade steps).
We fixed an issue where profiles could remain stuck in a Running state and skip scheduled runs for up to 10 minutes after a lost database connection, or after a service restart that interrupted a run. In addition, connection tests no longer interfere with ongoing profile collections.
We fixed an issue where filter selections could be lost. Filter selections (such as selected sensors, devices, or groups) are no longer cleared if the device tree loads incompletely. Your selections are now preserved even if objects become temporarily unavailable or invisible, for example due to access rights changes. A kept selection whose object is not in PRTG is shown as “Not found in PRTG” in the filter editor, where you can remove it.
We fixed an issue where filter sensor counts kept showing an outdated number when all selections for a PRTG server were removed or became unavailable. Filters now correctly show 0 sensors in those cases.
We fixed an issue where filter sensor counts were inflated by including sensors from unrelated groups whose names differed only by spaces, punctuation, or non-Latin characters. Each group now only reflects its own sensors in counts. The counts are correct after the first tree sync following the update.
We fixed an issue where running a status data collection could delete business processes belonging to other profiles that share the same target database. Business processes from other profiles are now correctly preserved.
We fixed an issue where business process components kept showing sensors from an earlier run when filter criteria returned no results. The component’s sensor list now clears as expected.
We fixed an issue where the Historic Data Polling service failed to start when the configuration database was unavailable at boot, and stayed stopped until it was started manually.
We fixed an issue where the name and machine of a deleted agent could not be reused.
We fixed an issue where new MSSQL target databases got a duplicate date column in the channel value table.
We fixed an issue where the License Information page sometimes showed outdated license details.
May 20, 2026 - PRTG Data Exporter 2026.5.20.610
Features
- We introduce multi-agent support, allowing you to deploy lightweight worker agents on remote machines so that PRTG Data Exporter can collect data from PRTG servers that are not directly reachable from your main installation, for example, PRTG servers inside isolated company networks when Data Exporter is running in the cloud. Worker agents are installed and managed centrally from the Data Exporter web interface.
- We added a status banner to all pages in PRTG Data Exporter that notifies you when a new version is available.
- We added a data collection status panel to all Grafana status dashboards.
- We now allow multiple PRTG servers with the same hostname to be added to PRTG Data Exporter. Each server is identified by its unique alias. This allows you to, for example, add several servers with the hostname 'localhost'.
- We added a safeguard that prevents you from configuring multiple profiles that export data from the same PRTG server to the same target database, avoiding duplicate or conflicting data exports.
- We improved how PRTG Data Exporter handles objects deleted from your PRTG installation. Deleted groups, devices, and sensors are now retained in the target database and marked as deleted.
- We added a new tools.exe reset-password command that lets administrators recover access to Data Exporter when a password is lost.
- We updated how timestamps are stored in target databases so that Grafana now displays data in the correct time for your time zone. The migration runs automatically in the background and existing data is preserved. Data collection continues as normal.
Changes
- We updated PRTG Data Exporter to run on .NET 10 and refreshed all associated packages to their latest versions. This improves performance, security, and long-term support.
- We updated the bundled PostgreSQL to the latest available PostgreSQL 17 minor release. Both new and existing local PostgreSQL installations managed by PRTG Data Exporter will be updated automatically.
- We updated the Grafana API integration to support Grafana version 12 and 13.
- We updated licensing to work across multiple agents in a multi-agent setup.
- We removed the internal configuration database from the list of selectable target databases.
Bugfixes
- We fixed an issue where PRTG Data Exporter failed to start on Windows systems with Hardware-enforced Stack Protection (CET Shadow Stack) enabled, resulting in an HTTP 502.5 error.
- We fixed an issue where deleting a business process in PRTG Data Exporter did not remove it from Grafana.
- We fixed an issue where renaming a component within a business process caused both the old and new component names to appear, resulting in duplicate entries.
- We fixed an issue where the Probes Free Space panel in the Grafana Probes Health dashboard appeared empty after initial setup. The default Probes Health metrics filter was missing the diskspacesensor tag.
- We fixed an issue where data collection could fail when parsing historic data from PRTG, caused by a summary row appended to the CSV response that had fewer columns than expected.
February 05, 2026 - PRTG Data Exporter 2026.1.22.503
Bugfixes
- We fixed an issue where license activation could break unexpectedly, requiring manual reactivation to restore functionality. This occurred in specific scenarios during online license validation, particularly when multiple profiles with identical schedulers were running.
November 13, 2025 - PRTG Data Exporter 2025.11.12.376
Features
- We added automatic license activation for online instances of PRTG Data Exporter.
- We updated the offline activation process.
For more information on how to activate your license, see the PRTG Data Exporter manual.
Changes
- We addressed the vulnerability in the ASP.NET Core. You can track this vulnerability in CVE-2025-55315. PRTG Data Exporter now requires as of .NET 9.0.10 or higher.
Bugfixes
- We fixed an edge-case issue where data collection failed to resume automatically, for example, after a server restart or a license key update.
August 14, 2025 - PRTG Data Exporter 2025.8.14.2
Important information: This update requires a clean installation of PRTG Data Exporter. Due to the nature of the changes in this version, you cannot install it over an existing PRTG Data Exporter installation. For more information, see the PRTG Data Exporter manual.
Features
- You can now combine data from multiple PRTG servers into unified, customizable Grafana dashboards. This new feature enables you to create a high-level overview over multiple PRTG servers tailored to your specific needs.
Changes
- PRTG Data Exporter now comes as a web-based application instead of a desktop application.
- PRTG Data Exporter now installs and uses PostgreSQL instead of Microsoft SQL Express to store its configuration.
Known issues
- In some cases, for example after a server restart or after you change your license key, data collection might not resume automatically. To make sure it resumes, open Windows Task Manager and check that the services PRTG Data Exporter | Historic Data Polling Task and PRTG Data Exporter | Tree Data Polling Task are running. Start the services manually if needed.
Solved with PRTG Data Exporter 2025.11.12.376
Disclaimer: PRTG Data Exporter streamlines the process of visualizing PRTG monitoring data by exporting it to standalone databases (MSSQL, PostgreSQL) that can be easily connected to Grafana® for powerful dashboard creation and data visualization via Grafana® APIs. Grafana® is a trademark of Grafana Labs. PRTG Data Exporter is not affiliated with or endorsed by Grafana Labs.
July 2, 2024 - PRTG Data Exporter 2024.5.28.2
Features
- We improved performance and significantly reduced the time required for collecting data by introducing parallel PRTG Historic Data request processing.
- Added new options when you configure a PRTG server:
- Degree of parallelism - specifies how many requests should be performed in parallel (default 2).
- Batch size - specifies how many requests should be processed in a single batch (default 50).
Changes
- Sensors saved in configuration and target databases now include the parent tags.
- Optimizations to the historic data requests to avoid making unnecessary requests and retrieving already existing data.
- The installer now uses ODBC Driver 18.
- The SA user for the SQL Server installation now uses a stronger password.
Bugfixes
- We fixed an issue where the PRTG server could not be added after initially specifying incorrect connection details.
- We fixed an issue where the About page would send an error when checking for updates, and no content would be displayed.
- We fixed an issue where TEMP tables were not being dropped from the Oracle DB after channel values were inserted.
November 10, 2026 - PRTG Data Exporter 2026.11.7.1050
Important
In order to update to this version, pay special attention to the following:
Worker agent permissions
If you run worker agents that were set up with an earlier version, update in this order:
Update the manager. This creates the new tables in the configuration database.
Run the updated agent setup SQL script on the configuration database.
Update the worker agents.
Without the script, data collection on those agents fails with a database permission error, and their logs don’t show up on the agent dashboard.
Grafana dashboards
Existing Grafana dashboards are not updated automatically, and deploying a dashboard again does not replace the existing one. After the update, delete any deployed dashboards and deploy them again from the Data Exporter UI. The new dashboards get new URLs, so update any bookmarks or links to them.
All dashboards need this to show times in your Grafana timezone and to show the new Stale and Paused statuses in their Data Collection Status panel.
Business Process - Overview and Business Process - Components also show Paused and Stale for business processes whose status data profile has stopped collecting.
Geo Map - Site Status and Geo Map - Connectivity are new. Deploy them from the Data Exporter UI.
Features
We added two new Grafana dashboards, Geo Map - Site Status and Geo Map - Connectivity, that show your sites, devices and groups on a map with their status, latency, bandwidth and site health, based on the GPS coordinates in the PRTG Location field. You can also show links per site, for example to camera feeds or runbooks, by adding them to the PRTG Comments field in this JSON format: {"pde":{"geomaps":{"metadata":[{"type":"link","value":"https://..."}]}}}. A plain URL in the Comments field is not picked up.
We added per-agent addresses for target databases. You can now set a host and port for each worker agent, for example when an agent reaches the database through a proxy, while Grafana and agents without their own address keep using the database’s central address. You manage these addresses in the target database dialog and the agent setup wizard. A failed collection now names the address that was used, in the logs and in the profile History tab.
We added a connection test per agent. The Target Database screen lists every active agent with the address it connects through and lets you test the connection from that agent. A failed test explains why, for example not reachable, no address configured or agent offline.
We added central agent logs. You can browse an agent’s log entries on the agent dashboard and filter them by level and date range. Old entries are deleted after 7 days by default, and you can change this period.
We added the Stale and Paused statuses. Profiles that stop collecting are shown as Stale in the Data Exporter and in Grafana, and profiles stopped on purpose are shown as Paused. Business processes also show Paused or Stale when their status data profile has stopped collecting, instead of keeping their last status.
We added a notifications bell to the top right of the top bar. It lists profiles whose last run failed or finished with warnings, and updates automatically after the next successful run.
Changes
We now confirm the start of a data collection at once: the profile shows Starting and then Running. A start is refused when a run of the profile is already queued or running, or when its agent is offline.
We now show an agent that stops responding as Offline faster, and an agent that comes back is online again within about a minute.
We simplified how you enter a PRTG server address: the separate Protocol and Port fields are replaced by a single URL field, for example https://your-server:port.
We added support for Microsoft SQL Server 2025.
We made the License Information page open faster. It keeps showing the number of used PRTG servers when a license check times out, and a successful license check is no longer reported as a timeout.
We made license key changes take effect without restarting the services.
We made data collection to PostgreSQL target databases more reliable through slow proxy chains: connections are reused, and a connection that hangs while opening is retried.
We made log detail messages selectable in the history view, so you can now easily highlight and copy text to paste into support tickets or search engines.
We improved PostgreSQL connection handling in multi-agent deployments, so several agents starting at the same time, for example after an update, no longer run into connection limit errors. The configured worker count is now respected.
We now digitally sign all Data Exporter executables and installers. Windows now shows Paessler as the verified publisher instead of “Unknown publisher”, which reduces security warnings during installation.
We sorted the schedule selection dropdown by duration instead of alphabetically, so shorter intervals appear at the top and longer ones at the bottom, making it easier to find the right schedule at a glance.
We improved tag-based saved filters. When reopening a saved filter configured with tags, objects now accurately show only the count of sensors matching the selected tags (instead of the total sensor count). In addition, warnings for invalid selections are now properly displayed.
We made updates with large PostgreSQL target databases more reliable. After the update, the channel value table is converted in batches in the background, so the migration no longer times out. While the conversion runs, data collection for the profiles that write to that database is paused. It resumes automatically when the conversion is done.
Bugfixes
We fixed an issue where agents that went Offline and came back did not get their scheduled jobs back until their services were restarted.
We fixed an issue where deleted profiles continued to appear in the Grafana Data Collection Status with their last result. Deleted profiles are now removed automatically.
We fixed an issue where Grafana dashboards always displayed times in UTC regardless of user timezone settings. Newly created dashboards now use Grafana’s default timezone, respecting your profile or browser settings (to apply this to existing dashboards, delete them and deploy them again as described in the upgrade steps).
We fixed an issue where profiles could remain stuck in a Running state and skip scheduled runs for up to 10 minutes after a lost database connection, or after a service restart that interrupted a run. In addition, connection tests no longer interfere with ongoing profile collections.
We fixed an issue where filter selections could be lost. Filter selections (such as selected sensors, devices, or groups) are no longer cleared if the device tree loads incompletely. Your selections are now preserved even if objects become temporarily unavailable or invisible, for example due to access rights changes. A kept selection whose object is not in PRTG is shown as “Not found in PRTG” in the filter editor, where you can remove it.
We fixed an issue where filter sensor counts kept showing an outdated number when all selections for a PRTG server were removed or became unavailable. Filters now correctly show 0 sensors in those cases.
We fixed an issue where filter sensor counts were inflated by including sensors from unrelated groups whose names differed only by spaces, punctuation, or non-Latin characters. Each group now only reflects its own sensors in counts. The counts are correct after the first tree sync following the update.
We fixed an issue where running a status data collection could delete business processes belonging to other profiles that share the same target database. Business processes from other profiles are now correctly preserved.
We fixed an issue where business process components kept showing sensors from an earlier run when filter criteria returned no results. The component’s sensor list now clears as expected.
We fixed an issue where the Historic Data Polling service failed to start when the configuration database was unavailable at boot, and stayed stopped until it was started manually.
We fixed an issue where the name and machine of a deleted agent could not be reused.
We fixed an issue where new MSSQL target databases got a duplicate date column in the channel value table.
We fixed an issue where the License Information page sometimes showed outdated license details.