Release notes for IBM Cloud Logs

Regions supporting new functionality and fixes:

• Dallas (us-south)
• Frankfurt (eu-de)
• London (eu-gb)
• Madrid (eu-es)
• Montreal (ca-mon)
• Osaka (jp-osa)
• Sao Paulo (br-sao)
• Sydney (au-syd)
• Tokyo (jp-tok)
• Toronto (ca-tor)
• Washington, DC (us-east)

For more information about the changes, see the 17 October 2025 Release notes

Regions supporting new functionality and fixes:

• Frankfurt (eu-de)
• London (eu-gb)
• Madrid (eu-es)
• Montreal (ca-mon)
• Osaka (jp-osa)
• Sao Paulo (br-sao)
• Sydney (au-syd)
• Tokyo (jp-tok)
• Toronto (ca-tor)
• Washington, DC (us-east)

For more information about the changes, see the 17 October 2025 Release notes

Regions supporting new functionality and fixes:

• Frankfurt (eu-de)
• London (eu-gb)
• Madrid (eu-es)
• Montreal (ca-mon)
• Sao Paulo (br-sao)
• Sydney (au-syd)
• Toronto (ca-tor)

For more information about the changes, see the 17 October 2025 Release notes

Regions supporting new functionality and fixes:

• Frankfurt (eu-de)
• London (eu-gb)
• Madrid (eu-es)
• Montreal (ca-mon)
• Sao Paulo (br-sao)
• Sydney (au-syd)

For more information about the changes, see the 17 October 2025 Release notes

Regions supporting new functionality and fixes:

• Frankfurt (eu-de)
• London (eu-gb)
• Montreal (ca-mon)
• Sao Paulo (br-sao)
• Sydney (au-syd)

For more information about the changes, see the 17 October 2025 Release notes

Regions supporting new functionality and fixes:

• London (eu-gb)
• Montreal (ca-mon)
• Sao Paulo (br-sao)
• Sydney (au-syd)

For more information about the changes, see the 17 October 2025 Release notes

Regions supporting new functionality and fixes:

• Montreal (ca-mon)
• Sao Paulo (br-sao)
• Sydney (au-syd)

For more information about the changes, see the 17 October 2025 Release notes

Regions supporting new functionality and fixes:

• Montreal (ca-mon)
• Sydney (au-syd)

For more information about the changes, see the 17 October 2025 Release notes

New features included in this release.

• Additional capabilities are now supported for alerts with the introduction of a new alert_definition API method. Changes are also made as a result to the IBM Cloud Event Notifications payload. See the following documentation topics for information about the alerts API changes and actions you might need to take as a result.

  • Considerations for new alert and priority configuration
  • Alert priorities
  • Terraform changes required to convert alerts

• [Alert] New support for multi-condition alerts.

• [Alert] New support for anomaly detection in metric alerts.

• Reserved Fields is a new function letting you make sure that important fields are always indexed and available for search in Priority insights.

• [Custom Enrichments] You can now view a custom enrichment in the UI and download a custom enrichment CSV file to your local system.

• [UI] Visual Explorer is a powerful new tool that integrates a multifunctional Explore display with customizable dashboard widgets, enhancing your ability to explore logs.

• [UI] The Logs view is enhanced to support a detailed view of an individual log record.

• [Query] CLI and API support is available for background archive queries (asynchronous archive queries).

• [DataPrime] Support is available for the following functions:

  • arrayContains
  • inArray

• [Incidents] Watch data now presents undetected values that triggered an alert. This gives visibility into undetected values that contributed to the alerts, making it easier to understand the full context of an incident.

Features that have been removed:

• The Datamap feature is removed and is no longer supported.

Issues that have been resolved:

• [Query] Fixed a bug where downloading large files in Asynchronous Archive Queries was failing.

• [Alert] Fixes an issue with Verify Alert where results were inconsistent.

• [UI]/[Views] Fixed a bug when managing text column fields in saved views was not working.

• [UI] Fixed a bug where layout settings were not restored when switching between views.

• [UI]/[CustomDashboards] Fixed a bug when a DataPrime query including groupby aggregation returned inconsistent results.

• [UI] Fixed a bug when switching between two saved views keeps the filters from the previous unsaved view.

• [All logs] Fixed a bug where segment.manifests files were stored under wrong path in IBM Cloud Object Storage.

• [Query] Improved a warning message displayed when querying from All logs to handle cases where the data might be deleted from the bucket because of a lifecycle policy.

• [Query] Fixed a bug where running a DataPrime query in Priority insights was failing.

• [UI]/[CustomDashboards] Fixed a bug where open in explore was not redirecting correctly to the Logs page.

• [Streams] Fixed a bug where the filtering query was producing unexpected results in some scenarios.

DataPrime now support the multigrouby operator.

DataPrime now supports the union operator.

DataPrime now supports the join cross operator

DataPrime now supports passing of query parameter values using $p.

Compact mode provides a simplified and streamlined view, enabling users to focus on active monitoring and querying without additional widgets, filters, or statistics.

Enhancements added to the share the URL functionality so you can share a URL of the the current view of the logs explore screen.

New extensions are available:

• Activity Tracking: Use to get insights into your IBM Cloud activity tracking data.
• IBM Cloud Kubernetes Service: Use to get insights into your IBM Cloud Kubernetes Service logs.
• IBM Cloud® Databases for MySQL: Use to get insights into your IBM Cloud® Databases for MySQL logs.
• IBM Cloud® Databases for PostgreSQL: Use to get insights into your IBM Cloud® Databases for PostgreSQL logs.

Variables can be configured as a placeholder for a value that is used in queries. When used in custom dashboards, your dashboard's queries update to display data for that value.

The following issues are resolved.

[Alerts] Fixed an issue where the log_example field in an alert notification was sometimes including a null value.

[Custom Dashboards] Fixed an issue where widgets from metrics data were intermittently failing to load.

[API] Fixed an issue in the alerts list API where the notification_payload_filters field contained empty values.

[Data Usage] Fixed an issue in the data usage graph where usage for some days was displayed as null.

[UI] Fixed multiple issue where the display of some screens in dark mode was broken.

[Alerts] Fixed an issue where condition_timeframe in notification didn't match the time frame/window defined in the alert configuration.

Geo enrichment now supports ASN (Autonomous System Number). ASN information will be added to the logs when geo enrichment is used.

DataPrime now support the join operator types inner, full, and left.

DataPrime now supports the stitch operator.

Support added so you can share the URL of the the current view of the logs explore screen.

The following issues are resolved.

• [UI] Resolved the issue in the custom dashboard where no data was shown in widgets when querying logs from priority insights.
• [UI] Resolved the issued where livetail did not display UTF-8 encoded characters.
• [UI] Resolve the issue when expanding the info panel hid the contents behind the navigation menu.

• [Query] - Fixed an issue where running a query in All Logs would result in a "Query Failed" message with no results returned even if the query ran up to the maximum timeout of 5 minutes.
• [Alerts] - Fixed an error where Metric alerts were not triggering notifications.
• [UI][Logs] - Fixed an issue where the selected keys in the Content column are reset when switching between Priority Insights and All Logs.

• [API][Views] - Fixed a bug where setting quick_selection using the API sets a custom selection in the UI.
• [UI][TCO] - Resolved an error when clicking Reset all overrides resulted in displaying ERROR: Failed to reset all overrides.
• [API][View Folder] - Fixed failure when updating view folders through the API.
• [API][Events2Metrics] - Fixed failure when updating Events to Metrics rules through the API.
• [Query] - Fixed query errors when using longer query windows, for example, for 6 or 12 hours.
• [UI] - Fixed an error where the dashboard login displayed intermittent HTTP 500 errors.
• [UI] - Fixed log highlighting for surrounding logs improving the ability to view the context around the logs.
• [Alerts] - Fixed an error where the alert payload was not sent as valid JSON.
• [UI][TCO] - Fixed an error where editing an existing TCO policy would wait to refresh for a long time.

• Fixed custom dashboards displaying "Something went wrong" when selecting Analyze and Alert.

IBM Cloud Logs is a service in the IBM Cloud.

For more information about the IBM Cloud Logs service, see Getting started with IBM Cloud Logs.