Backend release notes

See the following release notes:

• Release 1.0.321 (SaaS and self-hosted)
• Release 1.0.320 (SaaS only)

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 the following release notes:

• What's new in Instana
• What's new in Instana

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. This issue is now fixed.

Fixes:

SLO Smart Alerts did not trigger when a calendar‑month SLO was included in the alert configuration. This issue is resolved.

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:

• Multiple issues related to agent downloads are resolved.
• 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 issue is now resolved. 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:

• Multiple issues related to Agent downloads are resolved.
• 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 issue is now resolved. 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 exceeded 3000 characters, the message carrying these properties was discarded, which could result in the loss of all information in that message. This issue is resolved. Now even infrastructure properties with more than 3000 characters are properly handled.
• The alerting service did not correctly send alerts for vSphere metrics. This issue is resolved.

Fixes:

Fixes:

Fixes:

Fixes:

Fixes:

Fixes:

Fixes: