Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
87 lines (53 sloc) 4.6 KB

Change Log

[4.0.4] - 2019-10-27 WIP

Fixed

  • Memory Leak when using Grafana and PRTG plugin #109
  • Channel names now support bandwidth sensors correctly (speed and volume can be selected). #138
  • Slow performance from parsing XML - changed to native JSON #138

Changed

  • Dependency for lodash changed to 4.17.13.
  • Dependency for grafanaVersion changed to 6.3+ (mitigates vulnerability in lodash < 4.17.11)
  • POTENTIALLY BREAKING: Plguin retrieves data using historicdata.json now, in older versions of PRTG (17.x or older) the JSON was malformed. This appears to have been resolved at some point in the last two years. This should lead to a massive performance increase as it is no longer necessary to parse/transform XML into JSON.
  • moved pad function from PRTGAPIService to utils
  • Query builder: Channel names now come from directly from the values, this fixes a lot of issues.

Removed

  • sass tasks from Gruntfile.js
  • XML Parser

Added

  • Ability to specify metric value multiplier as a decimal, E.g., for converting Bytes from flow sensors to bits.

[4.0.3] - 2017-07-28

Fixed

  • Query Editor: Fixed structure of editor elements, alignment and other visual tweaks
  • API: Fixed an issue with some sensors where the displayed name is different from the name returned by the histdata XML query.

Added

Changed

  • Plugin: Cleaned up package.json and plugin.json, updated version number, updated plugin README.md, removed unused content, and, replaced PRTG logo image.

[4.0.2] - 2017-07-24

Fixed

  • API: Missed a bug that caused the query editor to show ALL sensors when Device was set to "*" even if Group was specified.
  • API: Added query string parameter "&count=9999" to group, device, and sensor queries to resolve issues for larger deployments. Addresses #49

Changed

  • API: Updated method to retrieve historic data, fixes an issue where no values are returned if the channel display name differes from the name in the API XML response. For instance, SSL Security sensors display the channel "Security Rating", when the actual value contains additional descriptive text.
  • API: Performance improvements in the collection of historic data, the array index to retrieve the channel value from is determined using the first result record instead of being determined for each result, which has a noticable impact with multiple-channel queries and thousands of data points.

Added

  • Query Editor: Added option to include a device's name in an item's label. Addresses #47

[4.0.1] - 2017-07-24

Fixed

  • Query Editor: Fixed color highlighting. Addresses #48

Changed

  • API: Updated method to retrieve historic data, fixes an issue where no values are returned if the channel display name differes from the name in the API XML response. For instance, SSL Security sensors display the channel "Security Rating", when the actual value contains additional descriptive text.
  • API: Performance improvements in the collection of historic data, the array index to retrieve the channel value from is determined using the first result record instead of being determined for each result, which has a noticable impact with multiple-channel queries and thousands of data points.

Added

  • Query Editor: Added option to include a device's name in an item's label. Addresses #47
  • API: Added query string parameter "&count=9999" to group, device, and sensor queries to resolve issues for larger deployments. Addresses #49

[4.0.0] - 2017-07-17

Fixed

  • PRTG Logo filename case, closed #36.
  • Fixed condition where some queries that fail cause Grafana to display an error message like "Cannot read property 'match' of undefined, closed #44

Changed

  • Templating: Proper support for multiple-value template items.
  • All code is ES6 compliant.

Added

  • Query Editor: Mutiple items can be selected from a single query.
  • Query Editor: Select from Raw JSON, Metrics, or Text property query mode.
  • Query Editor: Full regular expression support for all query filters.
You can’t perform that action at this time.