Backend release notes

See the following release notes:

• What's new
• Release 1.0.320 (SaaS only)

Fixes:

Resolved an issue that caused unexpected session invalidations and 401 redirect errors when you accessed the base domain in self-hosted SAML environments.

Fixes:

Updated HistogramDeltaValueExtractor to log malformed histogram discard messages at the DEBUG level instead of a higher log level, improving log clarity and reducing non-critical warnings.

Fixes:

Resolved an issue that caused inconsistencies in retrieving tag set data when republishing occurred without a rollover.

See 319 release notes in offline docs

Fixes:

Updated HistogramDeltaValueExtractor to log malformed histogram discard messages at the DEBUG level instead of a higher log level, improving log clarity and reducing non-critical warnings.

Improvements:

The zHMC platform now supports Capacity Group Utilization metrics. This enhancement improves visibility into capacity groups by delivering insights into:

• Configured capacity groups
• Defined capacity group values (capacity limits)
• Overall usage at the group level

This capability is available for zHMC sensors running on a guest partition with connectivity to the zHMC server.

Fixes:

LDAP login failed in single‑tenant, single-unit self‑hosted installations that use tenant and unit in the URL path instead of subdomains. You can now log in using LDAP.

Fixes:

You can now trigger SLO Smart Alerts when a calendar‑month SLO is included in the alert configuration.

Fixes:

LDAP login failed in single‑tenant, single-unit self‑hosted installations that use tenant and unit in the URL path instead of subdomains. This issue is now fixed.

Fixes:

• You can now download the agent without issues.
• The duration before a monitored entity was transitioned to the offline state was determined as a direct multiple of its configured poll rate. As a result, an entity with a 60‑second poll rate was not marked offline until approximately 20 minutes after it stopped reporting data. The collector now applies the corrected timeout. For entities with poll rates of 15 seconds or greater, a shorter and more consistent timeout is applied. For example, with a 60‑second poll rate, an entity is transitioned to the offline state after 5 minutes of inactivity.

Fixes:

LDAP login failed in single‑tenant, single-unit self‑hosted installations that use tenant and unit in the URL path instead of subdomains. This issue is now fixed.

Fixes:

• You can now download the agent without issues.
• The duration before a monitored entity was transitioned to the Offline state was determined as a direct multiple of its configured poll rate. As a result, an entity with a 60‑second poll rate was not marked offline until approximately 20 minutes after it stopped reporting data. The collector now applies the corrected timeout. For entities with poll rates of 15 seconds or greater, a shorter and more consistent timeout is applied. For example, with a 60‑second poll rate, an entity is transitioned to the Offline state after 5 minutes of inactivity.

Fixes:

• When infrastructure properties exceed 3,000 characters, the platform discards the message, which could result in loss of all information. The platform now properly handles properties with more than 3,000 characters.
• The alerting service now correctly sends alerts for vSphere metrics.

Fixes:

Fixes:

Fixes:

Fixes:

Fixes:

Fixes:

Fixes: