Skip to content

All versions since [8.2 Patch 1]

[8.2 Patch 1]

This release includes bug fixes only, plus general performance optimization.

Fixed

  • [PG-18135] GuardAgentTray.exe did not start and showed no login info.
  • [PG-18136] Agent tray was not added to run with the new installer.
  • [PG-18137] App creation failed.
  • [PG-18138] Fixed dashboard tagging.
  • [PG-18155] First agent delivery flushed the agent table.
  • [PG-18156] / [PG-18158] / [PG-18159] Process table was always empty.
  • [PG-18131] Locked the application-status-widget period.
  • [PG-18143] Improved cleanup of WGO (request/response) data from the database.

[8.2 Patch 2]

This release includes bug fixes only. It overwrites the PG service memory settings (initial 2048 / max 4096); reapply custom JvmMs / JvmMx values after upgrading, and run the Backend-Hotfix-810-91 hotfix script.

Fixed

  • [PG-18186] Too many processes in WGO.
  • [PG-18183] PerformanceGuard very slow after upgrading to 8.2.91.

[8.2 Patch 3]

This release includes bug fixes only. It overwrites the PG service memory settings (initial 2048 / max 4096); reapply any custom JvmMs / JvmMx values after upgrading, and run the Backend-Hotfix-823-91.sql hotfix script as the pguard database user.

Fixed

  • [PG-18207] Improved overall performance.
  • [PG-18208] Improved dynamic thresholds.

[8.3]

PerformanceGuard 8.3 integrates with CapaSystems’ cloud platform CapaOne. PerformanceGuard customers get free access to CapaOne Reliability (contact CapaSystems sales to have it added to the contract); it can only be integrated after upgrading both server and agents to 8.3.

This release contains an important security update — if you use CapaSystems Cloud Services, update as soon as possible to avoid degraded service.

Added

  • CapaOne Reliability — collects reliability information from all computers and shows it on a dashboard (requires the new CapaOne agent). PerformanceGuard integrates with it, so you can left-click a unit for direct access to its reliability information.
  • Agent detection of new Windows versions: Microsoft Windows 11 and Windows Server 2022.
  • CapaOne integration in the agent — collects the CapaOne agent identification; the CapaOne agent collects the reliability index and the Windows events that impact reliability.

Changed

  • Administrators now have access to all dashboards.
  • Web extensions are allowed without a computer policy.
  • Improved use of database indexes and statements.
  • Improved agent installer, stability, and hardening.

Fixed

  • [PG-18175] Missing performance counters.
  • [PG-18224] Native messaging extension crash with the latest Chrome and Edge Chromium.
  • [PG-18265] “Edit subnet group” slider broken.
  • [PG-18276] Search defect with multi-word queries.
  • [PG-18279] Improved client DNS resolution.
  • [PG-18290] Process dropdown always showed only “All Processes” in Hotspot Process Traffic.
  • [PG-18312] Agent now detects Windows 10+ versions correctly.
  • [PG-18322] Improved ServiceNow integration.
  • [PG-18325] Fullscreen-to-normal did not work on PG widgets.
  • [PG-18330] WGO: returning from Online status gave an error.
  • [PG-18338] Could not install 8.1-or-older version agents.
  • [PG-18340] Fixed agent memory usage.
  • [PG-18342] Tag data was never collected for Internet Explorer.
  • [PG-18372] Selected dashboards were not cleared after creating a slideshow.
  • [PG-18376] Physical memory free was not reported correctly.
  • [PG-18377] Unable to install the agent on a Core server.
  • [PG-18380] Moving servers from unmonitored to monitored failed.
  • [PG-18384] CI PG overwrote PG settings for com.capasystems.performance.
  • [PG-18385] Installing the CI or Enterprise agent stopped the pga-service.
  • [PG-18386] pga_updater was marked for deletion but never deleted.

Discontinued

  • Last server release that supports installation on Windows Server 2008 / 2008 R2 / 2012.
  • Internet Explorer filters are being phased out — start using the Chromium filters.

[8.3 Patch 1]

This release includes bug fixes only.

Fixed

  • [PG-18437] PG agent 8.3 could not connect to the 8.2.95 server.
  • [PG-18417] Location bubble chart defect.

[8.3 Patch 2]

This release includes bug fixes only.

Fixed

  • [PG-18474] Status message did not change after disabling the reindex job.
  • [PG-18528] Agent reconfigured protocol to 500 when delivering a static report.
  • [PG-18545] Hotfix scripts were not created when installing a new server.
  • [PG-18556] Error viewing event details.
  • [PG-18583] Scheduled reports did not wait for charts to load.

[8.3 Patch 3]

Security and bug fixes.

Fixed

  • [PG-18601] Missing statistics data in the dashboard PDF report.
  • [PG-18602] Upgraded the bundled jQuery and Jetty frameworks.

[8.3 Patch 4]

Security fixes plus a small dashboard enhancement.

Added

  • “What’s Going On” dashboard now supports filtering by location.

Fixed

  • [PG-18610] Unable to select agents through the OS dropdown.
  • [PG-18611] Deleting a web tag always deleted the last entry.
  • [PG-18612] Apache text vulnerability.

[8.3 Patch 5]

This release includes bug fixes only.

Fixed

  • [PG-18614] Display2 graphs did not work on first load (no PDF reports).
  • [PG-18615] Could not create or edit pings and traces.

[8.3 Patch 6]

This release includes bug fixes only.

Fixed

  • [PG-18623] Dashboard error — no REST call.

[8.3 Patch 7]

This release includes bug fixes only.

Fixed

  • [PG-18627] Application search defect.
  • [PG-18628] Problem with PerformanceGuard on production servers.
  • [PG-18630] “What’s Going On” dashboard not working after upgrading to 8.3.

[8.3 Patch 8] Latest

The current downloadable build is PerformanceGuard Server 8.3.94 (8.3 Patch 9) with the matching 8.3.x agent. This version requires a new license file — contact CapaSystems support before upgrading.

This release includes bug fixes only.

Fixed

  • [PG-18626] ServiceNow integration UI glitches.
  • [PG-18637] Datatype too short.
  • [PG-18638] Handle Citrix null-pointer exception.
  • [PG-18641] Agent install form broken.
  • [PG-18642] Unable to use secure SMTP.s