Support for new technologies

• Dell EMC VPLEX
• Dell EMC Metro Node

For further details refer to release notes.

Download link, upgrade manual

Check out our demo site for new features.

We will be attending these conferences as exhibitors in the near future:

• DTX + UCX, 29-30 April 2026, Manchester, UK
• IBM TechXchange, 26-29 Oct 2026, Atlanta, USA

When running XORMON 2.1, I started to note, that what data xormon displayed did not correlate with the HMC. Example the VIOB lpar had 4 cpus configured, but xormon showed 1. Another lapr was shrunk from 25 cores to 14, but xormon still shows 25.

I subsequently upgraded to 2.2 and three service packs, and the issue has become worse.

I am currently running on 2.2.50, and none of my LPARs show annual usage, server information, no resource configurator information.

At this point I am considering dropping xormon, in favour of lpar2rrd as it is a far more stable product.

This is not a once off issue I have had with this product, and has been on going issues since version 1.6.

Due to these issues and instability my client will not buy the product saying it is unreliable and ultimately junk compared to LPAR2RRD.

However lpar2rrd is expensive on resources and it is a no win for us.

I am currently testing Xormon-ng and noticed a possible discrepancy regarding HPE 3PAR metrics.

According to the compatibility matrix:

https://xormon.com/feature-matrix.php

the parameter blocksize should be collected for 3PAR systems.

However, in our environment this metric is not present.

Additionally, it also appears to be missing in the public demo:

https://demo.xormon.com/storage/device/HPE_3PAR-01/pool-io?item_id=cb8c6332-a820-4cb9-bd9c-56bc862fd921

Could you please clarify:

• Is blocksize currently supported for HPE 3PAR in Xormon-ng?
• Are there any specific configuration requirements to enable its collection?
• Or is the compatibility matrix outdated regarding this metric?

Thank you in advance for your clarification.

When using the command "./xormon.sh status" i ve got this message:

Loading environment from server-nest/.env

>>>> In-memory PM2 is out-of-date, do:

>>>> $ pm2 update

In memory PM2 version: 5.4.3

Local PM2 version: 6.0.14

Do i have/need to update PM2?

./xormon.sh ver

Loading environment from server-nest/.env

Versions

--------------------

Backend : 2.2.30

Node.js : v24.13.0

NPM   : 11.6.2

Thank you

Br,

Alexandre

I've uploaded the server certificates to Xormon. Unfortunately, I had a typo in the alias and had to reapply.

Now I can't change the certs in the Application => SSL Cert section anymore.

I "Click to Upload crt / key" give it the files and click on "Upload & Apply" but nothing happens.

A reload of the WebGui is not helping and a container restart also didn't work.

I deleted the certificates in the folder manually to check if I can upload the new ones. Not working.

Also, I have a question about renewing the certs. We are using the salt stack to manage our servers incl. the certs. So if salt would place the new cert files in the folder ./files/cert would it be recognized by Xormon, or do I have to restart the container?

Many thanks in advance.

Kinds regards,

Jörg

We are running XorMon appliance and pulling metrics on our VMware Cluster, it has been awhile since I had to drill into VM details, but today noticed that I can't do this, I see the VM in the "VM TOP" page, however the VM itself does not appear in the list of VMs (bunch of VMs missing, only a few actually show up).

Not sure why this is not working, we are on VMware vCenter v8.0.3 build 24674346 with ESXi 8.0.3 build 24674464.

Below is the XorMon-NG version details:

XorMon 2.1.10

Node.js v20.18.0

Frontend 2.1.10

Database timescale/2.16.1

Appliance 1.6.10

Also attached is the error we get, any idea what the issue or how I can fix this?

Using XorMOn-NG 2.1.10 (VMware OVA), trying to upgrade to latest (xormon-ng-2.2.30.tar.gz), running into issue below, is there anything that I am missing in my upgrade steps?

xormon@Van-XorMon:~/xormon-ng$ ./xormon.sh upgrade /home/xormon/xormon-ng-2.2.30.tar.gz

Loading environment from server-nest/.env

=============================================================================

Installing upgrade ...

Running pre-upgrade script...

Error running pre-upgrade script: Error: Command failed: node /home/xormon/xormon-ng/server-nest/files/tmp/upgrade/server-nest/dist/pre-upgrade.js

/home/xormon/xormon-ng/server-nest/files/tmp/upgrade/server-nest/dist/service/configuration/App.js:9

const uuid_1 = require("uuid");

        ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /home/xormon/xormon-ng/server-nest/files/tmp/upgrade/server-nest/node_modules/uuid/dist-node/index.js from /home/xormon/xormon-ng/server-nest/files/tmp/upgrade/server-nest/dist/service/configuration/App.js not supported.

Instead change the require of index.js in /home/xormon/xormon-ng/server-nest/files/tmp/upgrade/server-nest/dist/service/configuration/App.js to a dynamic import() which is available in all CommonJS modules.

  at Object.<anonymous> (/home/xormon/xormon-ng/server-nest/files/tmp/upgrade/server-nest/dist/service/configuration/App.js:9:16) {

 code: 'ERR_REQUIRE_ESM'

}

Node.js v20.18.0

An error occurred while running the pre-upgrade script. Please check the logs for more details.

=============================================================================

STARTING AFTER INSTALL / UPGRADE...

Connection to database postgres was successful!

Looking for database xormon

Connection to database xormon was successful!

Exiting verify.ts...

Application launched successfully

xormon@Van-XorMon:~/xormon-ng$ npm list uuid

/home/xormon/xormon-ng

└── (empty)

We planned to migrate our licensed lpar2rrd/stor2rrd instances to Xormon container with Podman.

We've build a sandbox for testing Xormon in container.

Is there anyway to configure Hitachi VSP export tools in container with Podman ?

Regards.

After install several AIX/VIO agent I cannot see the agent data in the UI

where can I look to see what the problem is?

Thank you - UMBERTO

We are trying to connect IBM Cloud (Frankfurt location) into Xormon NG monitoring. And we have questions:

• what IP addresses we should open in network firewall to allow Xormon get access to IBM Cloud?
• is there any way to configure Xormon accessing IBM Cloud IPs via HTTP proxy?

Regards,

Michael

I've observed that vSAN datastore metrics are missing in UI (see attached screenshot).

Currently running:

Xormon: XorMon2.2.10, Node.jsv24.13.1, Frontend2.2.10

vCenter: 9.0.1.0 Build: 24957454

Is it possible to add this data in XorMon?

Connection test results:Microservice is not active

Microservice Perl prerequisites not satisfied:

Missing Perl module: Xorux_lib

My appliance is w free edition (Debian GNU/Linux 12 (bookworm))

Versions: XorMon2.2.0,Node.jsv24.14.0,Frontend2.2.0,Databasetimescale/2.22.1,Appliance2.0.0

Please give me some suggestions on how to add the missing module. I can't find it in the system, and AI doesn't suggest anything either.

cpan install Xorux_lib -> >(error): Skipping Xorux_lib because I couldn't find a matching namespace.

First of all, I want to say that you've done an excellent job, and the new product looks impressive — thank you for your effort.

I am adding a NetApp FAS2750 running ONTAP 9.13.1 to Xormon 2.2, but for some reason, the GUI does not display read and write latencies for volumes, SVM, or aggregates (only drive latency is available).

Also, no statistics are available for any PORT aka ETH interface.

I tried adding it as FAS CDOT or ONTAP SELECT — there is no data for resp_t_read or resp_t_write. I used the admin account to eliminate any permissions issues.

Is it possible to get latency data in the new product?

Thank you in advance.

Support for new technologies

• IBM TS3k
• XenServer / Citrix / XCP-ng
• HPE OneView

Note: Node.js v24 is required for this XorMon version, upgrade to it before XorMon v2.2.0 upgrade as per this docu.

For further details refer to release notes.

Download link, upgrade manual

Check out our demo site for new features.

We will be attending these conferences as exhibitors in the near future:

• VMUG Connect, 17-19 March 2026, Amsterdam, Netherlands
• Cloudfest, 23-25 March 2026, Europa-Park, Germany
• DTX + UCX, 29-30 April 2026, Manchester, UK
• IBM TechXchange, 26-29 Oct 2026, Atlanta, USA

See what our alerting implementation can provide you: https://www.youtube.com/embed/whAwdlet3Qw

Using xormon-ng appliance, updated to latest 2.1.10 version to monitor our two tape libraries, they are:

IBM TS4300 v1.4.1.0-B00

Dell EMC ML3 v1.5.0.0-A00

Both fail with:

API authentication status

Authentication failed: Authentication failed on all login endpoints

I have added a xormon user to both libraries, and the role is "monitor" as per the docs. Not sure what the issue is.

Anyone able to help me out?

Hello everyone.

I am a long time Stor2rrd user.

Happy with the new Xormon NG. The best tool as I know.

Performance alerting and anomaly detection are useful features.

But the HW Event target of the Integration is broken. As the image shows, the Integration does not work with HW events. Cannot save configuration when Alert metric is turned on and off.

This issue needs to be fixed soon.

Thanks in advance.

If you install the lpar2rrd-agent on X86 Linux System a service called "lpar2rrd-agent.service" is configured.

This script getsysuuid.sh runs once after reboot and creates a file called ".uuid" in the home dir of lpar2rrd user. I guess it is used to give lpar2rrd or xormon a chance to match the data from vcenter to the agent data.

Ideas for improvment:

The file ".uuid" should be owned by lpar2rrd and read for others should be removed. In the script getsysuuid.sh is already an "chmod 444". Please add a chown lpar2rrd and chmod 440 to the script.

Reason: Security Standard CIS requires to not have any "for other readable files" in home dirs of users.

The script is startet with "Type=oneshot" and "RemainAfterExit=true". Is there a reason the service should reamain? We would prefere "RemainAfterExit=false"

What is your opinion to this little changes?

Regards Stefan

I upgraded my XorMon server this morning from version 2.0.11 to 2.1.0 using the CLI method. The script output shows that the upgrade completed successfully and the application was restarted, but the script hasn't exited and is still hanging. It looks like there is a "node" process still running that spawned from the xormon.sh script:

xormon  254926 254922 5 10:44 pts/0  00:00:26 node dist/cli-upgrade /tmp/xormon-ng-2.1.0.tar.gz

Will this eventually time out or complete? If not, can it be killed? What is this node process attempting to do?

Thanks!

Support for new technologies

• Commvault Backup and Recovery
• MongoDB
• OpenZFS
• Tape Library:
  • IBM TS2/3k
  • Imation LR
  • Dell PowerVault TL
  • Overland NEO

For further details refer to release notes.

Download link, upgrade manual

Check out our demo site for new features.

We will be attending these conferences as exhibitors in the near future:

• VMUG Connect, 17-19 March 2026, Amsterdam, Netherlands
• Cloudfest, 23-25 March 2026, Europa-Park, Germany

See what our topology implementation can provide you: https://www.youtube.com/embed/D9xSm8TriLY

additional to the mail. We did not get performancedates from X*/Brocade/Rest-API

How can we adjust this?

2025-10-07 09:40:08: [lalalalala] 9-14: sampling-interval=2 Must be 5, stats skipped...

2025-10-07 09:40:08: [lalalalala] 9-13: sampling-interval=2 Must be 5, stats skipped...

2025-10-07 09:40:08: [lalalalala] 9-12: sampling-interval=2 Must be 5, stats skipped...

2025-10-07 09:40:08: [lalalalala] 9-11: sampling-interval=2 Must be 5, stats skipped...

I’ve configured a NetApp E-Series 2806, Version 08.80.00.00, in Xormon 1.9 which only showed data for the current day.

After upgrade to 2.0.11 I can see data for the last 2 weeks, but not further back.

If I set custom date, e.g. “2025/10/29 14:31 – 2025/11/12 14:30” XorMon shows data, but for “2025/10/29 14:30 – 2025/11/12 14:30” no data are shown.

Regards,

Arndt

we only allow hostssl connections to all PostgreSQL databases (including the Xormon repository database). But during the installation we always get connections errors to the database. Can Xormon connect to PostgreSQL database with hostssl only in the pg_hba.conf?

The DB team already created the xormon user and the xormon database (and all other requirements like timescaleDB extension). It is possible to skip the db creation step during installation?

we want to install a new xormon environment. Because we have other PGS installations we used version 18.0

During xormon.sh start I get the following:

query: CREATE TABLE "migrations" ("id" SERIAL NOT NULL, "timestamp" bigint NOT NULL, "name" character varying NOT NULL, CONSTRAINT "PK_8c82d7f526340ab734260ea46be" PRIMARY KEY ("id"))

query failed: CREATE TABLE "migrations" ("id" SERIAL NOT NULL, "timestamp" bigint NOT NULL, "name" character varying NOT NULL, CONSTRAINT "PK_8c82d7f526340ab734260ea46be" PRIMARY KEY ("id"))

error: Error: Connection terminated unexpectedly

In the PGS log I see:

logged>",,,,,,,,,"","client backend",,6759126417701275427

2025-11-17 09:31:11.655 CET,"postgres","xormon",33891,"127.0.0.1:24256",691add4f.8463,12,"CREATE SCHEMA",2025-11-17 09:31:11 CET,84/0,0,LOG,00000,"duration: 0.335 ms",,,,,,,,,"","client backend",,6759126417701275427

2025-11-17 09:31:11.723 CET,,,1649,,691ad1f4.671,9,,2025-11-17 08:42:44 CET,,0,LOG,00000,"background worker ""Job History Log Retention Policy [3]"" (PID 33894) was terminated by signal 11: Segmentation fault","Failed process was running: CALL _timescaledb_functions.policy_job_stat_history_retention()",,,,,,,,"","postmaster",,0

2025-11-17 09:31:11.723 CET,,,1649,,691ad1f4.671,10,,2025-11-17 08:42:44 CET,,0,LOG,00000,"terminating any other active server processes",,,,,,,,,"","postmaster",,0

We get this a segmentation fault. The DB crashes and cannot be restarted. We have to remove in postgres.auto.conf the timescaledb

shared_preload_libraries = 'pg_stat_statements, pgaudit, set_user, pgcrypto, credcheck,timescaledb'

We starte the DB cluster, drop the xormon DB and we can restarted it with timescaledb extension enabled.

 Anyone else to it run with PGS 18.0 and timescale timescaledb-2-postgresql-18-2.23.1-0.el9.x86_64?

We are just in the process of setting up out new XORMON (we have a LPAR2RRD instance as well).

We are setting up our first IBM i agent and get the following error in the XORMON logs, any idea what we might have missed during the setup ?

2025-09-25 08:51:15: 2026 No mapping for 78XXXXX, EvoiDev3

The agent establishes a connection ok, and we have left it running overnight but no change, this message pops up every 20mins.

I configured two our Brocade SANs to be monitored by Rest API and have the same issue on both.

After 15 -20 minutes of SAN scanning, the Max limit for REST sessions reached error is shown in the log and no more data are collected.

Here is part of its log:

2025-11-04 11:40:00: [SAN_A] Cannot login to Rest API! Exiting... 

2025-11-04 11:40:00: [SAN_B] Cannot login to Rest API! Exiting... 

2025-11-04 11:40:00: [SAN_B] JSON body  : {} 

2025-11-04 11:40:00: } 

2025-11-04 11:40:00: } 

2025-11-04 11:40:00:  ] 

2025-11-04 11:40:00:  } 

2025-11-04 11:40:00:   } 

2025-11-04 11:40:00:   "error-module": "rest" 

2025-11-04 11:40:00:   "error-code": 14, 

2025-11-04 11:40:00:   "error-info": { 

2025-11-04 11:40:00:   "error-message": "Max limit for REST sessions reached", 

2025-11-04 11:40:00:   "error-app-tag": "Error", 

2025-11-04 11:40:00:   "error-tag": "operation-failed", 

2025-11-04 11:40:00:   "error-type": "application", 

2025-11-04 11:40:00:  { 

2025-11-04 11:40:00:  "error": [ 

2025-11-04 11:40:00: "errors": { 

2025-11-04 11:40:00: [SAN_B] Request error: { 

2025-11-04 11:40:00: [SAN_B] Request error: 403 Forbidden 

2025-11-04 11:40:00: [SAN_B] POST url     : https://192.168.xxx.yyy/rest/login 

2025-11-04 11:40:00: [SAN_A] JSON body  : {} 

2025-11-04 11:40:00: } 

2025-11-04 11:40:00: } 

2025-11-04 11:40:00:  ] 

2025-11-04 11:40:00:  } 

2025-11-04 11:40:00:   } 

2025-11-04 11:40:00:   "error-module": "rest" 

2025-11-04 11:40:00:   "error-code": 14, 

2025-11-04 11:40:00:   "error-info": { 

2025-11-04 11:40:00:   "error-message": "Max limit for REST sessions reached", 

2025-11-04 11:40:00:   "error-app-tag": "Error", 

2025-11-04 11:40:00:   "error-tag": "operation-failed", 

2025-11-04 11:40:00:   "error-type": "application", 

2025-11-04 11:40:00:  { 

The XorMon creates multiple Rest API connections and after it creates three of them, error rised.

admin> mgmtapp --showsessions

The following is the history of logins to the switch from external applications

(Login Timestamp, IP Address, User Account, Application, SessionId, Current VF, Auth Token, Protocol, UUID):

. . .

The following are the sessions from the external applications that are currently active:

2025/11/04-12:16:05.393245, 192.168.xxx.yyy, Monitor, libwww-perl/6.68, d7764c143b6be7bc694fa38e36d2f905676348694c13dacb757f859b77a27c31, -1, No, HTTPS, None

2025/11/04-12:26:05.464356, 192.168.xxx.yyy, Monitor, libwww-perl/6.68, 8fadb016d776d3e88494bd9761edb0e293a228a003829c1ac408e12102efddf0, -1, No, HTTPS, None

2025/11/04-12:31:05.563756, 192.168.xxx.yyy, Monitor, libwww-perl/6.68, 08d0c000433b1e1e31cce8b5430d3a98d73823e7a443d2c9e90659da9b88c2bb, -1, No, HTTPS, None

Both SANs have the same, standard Rest config with enabled KeepAlive as described at https://xormon.com/install-network.php#SAN-RESTAPI:

admin> mgmtapp --show

 REST Configuration:

    Interface State: Enabled

    Effective Protocol: HTTPS only

    HTTP State: Enabled

    Session Count: 3

 HTTPS Configuration:

    KeepAlive : Enabled

    KeepAliveTimeout : 15sec

Is there something I am missing? Where can be the problem?

Regards,

Zoran

For more context, we have xormon-ng and timescaledb containers running. The docker filesystem is around 1TB of space:

Filesystem            Size Used Avail Use% Mounted on

/dev/mapper/vg_data-varlibdocker 1008G 354G 654G 36% /var/lib/docker

In this chart you can see that every 2h more or less it gets full and cleans itself:

After connecting to the container shell we found lot of pgsq_tmp fles being generated in /var/lib/postgresql/data/base/pgsql_tmp

144a1b83e2b4:/var/lib/postgresql/data/base/pgsql_tmp# du -sm *

1025  pgsql_tmp2003098.0

1025  pgsql_tmp2003098.1

1025  pgsql_tmp2003098.10

1025  pgsql_tmp2003098.100

1025  pgsql_tmp2003098.101

...

144a1b83e2b4:/var/lib/postgresql/data/base/pgsql_tmp# du -sh .

265.0G .

144a1b83e2b4:/var/lib/postgresql/data/base/pgsql_tmp# ls | wc -l

273

For some reason is not using all the memory the OS has available and then it writes query temp files to disk:

Any idea how to fix it?

Versions used:

I was pleased to learn that this new version would include SSO. I was looking for it so I tested straight away.

Unfortunately, I can't get it to work, I will always get a popup with the error:

And this, despite I have the redirect URL configured to a regex https://xormon.mydomain/api/oidc/v1/*

I've also tried to both strict URL mentioned in documentation, this didn't change.

I share my Xormon SSO configuration just in case:

PS: I've many apps already working with the same Authentik instance

Thanks in advance! 😉👌

I am currently testing XorMon as monitoring solution for our Company.

Currently, my biggest issue is not getting data from Proxmox cluster.

Connection test passes with no issues.

No data are collected. In log following errors are shown:

2025-10-30 12:40:02: Use of uninitialized value $mac_address[2] in join or string at /home/xormon/xormon-ng/server-nest/microservices/proxmox/proxmox-service.pl line 335.

2025-10-30 12:40:02: Use of uninitialized value in string eq at /home/xormon/xormon-ng/server-nest/microservices/proxmox/proxmox-service.pl line 328.

2025-10-30 12:20:12: Not an ARRAY reference at /home/xormon/xormon-ng/server-nest/microservices/proxmox/proxmox-service.pl line 327.

Any idea where to look?

Regards,

Zoran

I have configured the LDAP on the new version XORMON-NG, and actually works since I can login with my AD user.

The problem is that the AD's users not appears in users and I can not assign permissions to view devices.

The LDAP groups are detected correctly but users not

Anyone knows why?

Thanks