Release notes for IBM Cloud Logs

Use these release notes to learn about the latest updates to IBM® Cloud Logs.

For release notes about the IBM Cloud Logs migration tool, see Release notes for the IBM Cloud Logs migration tool.

6 February 2025

Context-based restrictions: IBM Cloud Logs now supports context-based restrictions (CBR). For more information see, Protecting resources with context-based restrictions.

Notice regarding successful IBM Cloud Object Storage read activity tracking events: IBM Cloud Activity Tracker Event Routing drops successful cloud-object-storage.object.read events that are initiated by IBM Cloud Logs instances because they are not needed. For more information see Why am I not seeing successful read activity tracking events for IBM Cloud Object Storage activity generated by IBM Cloud Logs?.
Documentation about using regex for queries: Additional information is available about using regex for queries. For more information, see Using regex when querying data.

[UI][LiveTail] Livetail support

Livetail now supports Application and Subsystem drop-down filters which can be used to filter logs based on Application and Subsystem.

Fixes implemented

The following issues are resolved.

[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.

Fixes implemented

The following issues are resolved.

[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.

Fixes implemented

The following issue is resolved.

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

Documentation updates affecting IBM Cloud Logs and IBM Cloud Logs Routing: Significant documentation updates have been made to the IBM Cloud Logs and IBM Cloud Logs Routing documentation sets with information related to using agents to send data to IBM Cloud Logs moved from the IBM Cloud Logs Routing documentation to the IBM Cloud Logs documentation.

Osaka (jp-osa) and Sao Paulo (br-sao) region support: Osaka and Sao Paulo are now online regions for the IBM Cloud Logs service in the IBM Cloud. IBM Cloud Logs instances can now be provisioned in Osaka and Sao Paulo.

London (eu-gb), Sydney (au-syd), and Tokyo (jp-tok) region support: London, Sydney, and Tokyo are now online regions for the IBM Cloud Logs service in the IBM Cloud. IBM Cloud Logs instances can now be provisioned in London, Sydney, and Tokyo.

Washington (us-east) and Dallas (us-south) region support: Washington and Dallas are now online regions for the IBM Cloud Logs service in the IBM Cloud. IBM Cloud Logs instances can now be provisioned in Washington and Dallas.

Toronto (ca-tor) region support: Toronto is now an online region for the IBM Cloud Logs service in the IBM Cloud. IBM Cloud Logs instances can now be provisioned in Toronto.

IBM® Cloud Logs is generally available

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.