What's new in InformixHQ

You can segregate data, storage space, and processing resources for multiple client organizations by creating multiple tenant databases in a single instance of Informix server. A tenant is an isolated administrative and resource boundary that can be configured with its own storage spaces, memory limits, connection limits, VP class binding, logging mode, and locale.

Support for multitenancy is introduced in InformixHQ. Using InformixHQ UI, you can manage tenant databases end to end.

InformixHQ Operating System Disk Utilization sensor monitored operating system disk usage for the cooked storage devices used by the Informix database server. With the extended support for raw devices, when a raw chunk path is detected under /dev, the sensor calculates total, used, and free bytes for the raw device. This allows storage metrics to accurately reflect logical raw chunk usage by Informix database server.

InformixHQ now allows users to create unencrypted spaces even when DISK_ENCRYPTION is enabled.

On the "Create Space" page, a new checkbox is available: "Disk encryption is enabled by default. Uncheck to create an unencrypted dbspace." This checkbox is visible whenever the DISK_ENCRYPTION parameter is configured in the onconfig file. To create an unencrypted space, you should uncheck this option. You can verify the encryption status in the "Spaces" table under the "Encryption" column; unencrypted spaces are marked with a cross icon.

Starting InformixHQ 3.3.0, by default, InformixHQ suppresses duplicate incidents for the same alert and entity while the server is running. Once an incident exists for a specific condition, additional evaluations producing the same message will not create new incidents. A new incident will only be generated if there is a change in the underlying state or message. This is an improvement over earlier releases, where multi-entity alerts could generate new incidents during every evaluation cycle even without status changes.

The new Backup Age per dbspace sensor is designed for threshold-based alerting when a Level 0 backup is overdue for any dbspace.

The sensor monitors the age of the most recent Level 0 backup across all dbspaces and can trigger alerts based on your specific requirements (e.g., if 12 or 24 hours have passed since the last backup). This functionality helps administrators quickly identify backup gaps and mitigate potential recovery risks.

The Agent repository database space is full. This means the agent will not be able to store sensor data, resulting in data loss. Please add a new  chunk or  expand the database space.