Skip to content

Qonda Monitor Server AIO 2.0.3

Latest
Latest

Choose a tag to compare

View all tags
@ope-nz ope-nz released this 27 Sep 20:57
· 1 commit to main since this release
2.0.3
a79ea29
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release Notes

Qonda Monitor 2.0.3 · Agent 2.0.9

Highlights

  • FME job monitoring now records queue wait, engine, repository, submitting user, warning counts and failure messages — with new Jobs Summary and Job History reports.
  • Portal sign-ins are captured again. Portal 12.x moved browser logins to the security audit log; the agent now reads and merges both log sources.
  • Redesigned agent pages — every product page leads with a plain verdict ("Portal for ArcGIS is healthy") and status chips, with dark mode.
  • Data Store health corrected — the relational role is read properly, and two checks that reported false failures were removed.

Server and Dashboard

Agent connectivity

  • New /tokencheck endpoint. Agents can now verify their upload token without sending data, so the agent's own status page can state definitively whether its credentials are accepted.

Ingest

  • FME job records accept the additional job detail agents now send: queue wait, engine, repository, FME user, warning count and failure message. These fields are optional, so agents of mixed versions can report to the same server.
  • Portal activity records accept the security audit log's extra fields — result status, source IP, user agent and actor role — again as optional fields.

Reports

  • Two new reports: FME Jobs Summary (job counts, run times, queue waits and status breakdown per workspace) and FME Job History (individual runs with status, queue wait, engine and failure message).
  • Fixed: Portal Activity report returned no data. The host parameter was not being passed to the query.
  • Service Summary now filters the service list to the selected ArcGIS Server, and keeps your selection when the server changes.

Dashboard

  • "FME Failed (24h)" stat card on the Overview page, shown on organisations that have FME hosts reporting.

Agent

Redesigned status pages

  • Each product page now opens with a verdict banner and a row of status chips. Hovering a chip shows the full check detail; a failing check names what failed rather than just showing a red mark.
  • Health strips are time-slotted across the last 60 minutes, distinguish "no data" from "down", and name the failing check in the hover tooltip.
  • Dark mode, toggled from the navigation bar and remembered per browser.
  • Charts fill the page width at a consistent height and use a colour-blind-tested categorical palette. Status colours are no longer used for data lines, so a green line no longer implies "healthy".
  • Host Info and Utilization are now one "Host" page, showing detected products, hardware summary and live utilization together. Disk Info is renamed "Disks". Old links to host_info.html, utilization.html and disk_info.html no longer resolve.

Monitoring

  • Agent page shows upload token validity and upload pipeline status, plus the time of the last successful upload.
  • Log directory paths now show a file count, e.g. [142 log files].
  • ArcGIS Data Store: relational primary/standby role is read from relational-config.json; the port 9840 "memcache" check (never a relational port) was removed; the object store HTTP port typo was corrected (29878).
  • Portal log directory is resolved from portal-config.properties rather than guessed, and an empty arcgis-logsettings.json no longer breaks ArcGIS Server log discovery — both now report clearly when a directory cannot be determined.
  • ArcGIS patch checks only run when ArcGIS is installed.

FME log collection

  • Job records merge the engine job log with the core server log, adding queue wait time, engine name, repository, FME user, and — on failure — the error message.
  • Warning counts are captured from the job summary. Failed translations are recognised correctly (previously only successful ones were).

Configuration

  • The Config page can be populated from an existing config.json. The file is read in the browser and never uploaded; nothing is saved until you click Save Config.
  • A config.json placed beside the agent installer is copied into the installation folder before the service starts, so an agent can be deployed already configured. See Agent Installation.

Upgrading

Upgrade the server first, then the agents.

Administrators can upgrade in place from Config → System in the dashboard: the page shows the installed and available versions, and Upgrade & Restart downloads the new version, validates its checksum, applies it and restarts the service. Alternatively, run the new installer over the existing installation.

Older agents continue to work against the new server. A newer agent reporting to an older server simply will not record the new FME and Portal fields, and its token check will report "not verified".

Configuration and database data are preserved, and no schema migration is required.

Assets 4
Loading