---
name: cloud-logs-release-notes
title: Release notes for IBM Cloud Logs
description: Use these release notes to learn about the latest updates to IBM® Cloud Logs.
last-updated: 2026-11-03
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/cloud-logs?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Release notes for IBM Cloud Logs
{: #logs-release-notes}

Use these release notes to learn about the latest updates to IBM® Cloud Logs.
{: shortdesc}


## 26 October 2026
{: #cloud-logs-oct2626}
{: release-note}

The newly released IBM Cloud Logs CLI plugin version 0.7.0 includes a context request header in all REST API requests.








## 10 September 2026
{: #cloud-logs-sept1026}
{: release-note}

Release of the IBM Cloud Logs CLI plugin version 0.6.0, which includes the security remediation for CVE-2024-24790. 


## 21 August 2026
{: #cloud-logs-aug2126}
{: release-note}

Release of the Logging agent version 1.9.1
:   For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-aug2126)


## 13 July 2026
{: #cloud-logs-jul1326}
{: release-note}

Release of the Logging agent version 1.9.0
:   For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-jul1326)



## 18 June 2026
{: #cloud-logs-june1826}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)
    * Montreal (`ca-mon`)
    * Toronto (`ca-tor`)
    * Sydney (`au-syd`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)
    * Osaka (`jp-osa`)
    * Washington, DC (`us-east`)
    * Tokyo (`jp-tok`)
    * US South (`us-south`)
    * Mumbai (`in-mum`)


## 16 June 2026
{: #cloud-logs-june1626}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)
    * Montreal (`ca-mon`)
    * Toronto (`ca-tor`)
    * Sydney (`au-syd`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)
    * Osaka (`jp-osa`)
    * Washington, DC (`us-east`)
    * Tokyo (`jp-tok`)
    * US South (`us-south`)


## 15 June 2026
{: #cloud-logs-june1526}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

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


## 11 June 2026
{: #cloud-logs-june1126}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)
    * Montreal (`ca-mon`)
    * Toronto (`ca-tor`)
    * Sydney (`au-syd`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)
    * Osaka (`jp-osa`)
    * Washington, DC (`us-east`)


## 10 June 2026
{: #cloud-logs-june1026}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)
    * Montreal (`ca-mon`)
    * Toronto (`ca-tor`)
    * Sydney (`au-syd`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)
    * Osaka (`jp-osa`)


## 09 June 2026
{: #cloud-logs-june0926}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)
    * Montreal (`ca-mon`)
    * Toronto (`ca-tor`)
    * Sydney (`au-syd`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)


## 08 June 2026
{: #cloud-logs-june0826}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)
    * Montreal (`ca-mon`)
    * Toronto (`ca-tor`)
    * Sydney (`au-syd`)
    * London (`eu-gb`)


## 04 June 2026
{: #cloud-logs-june0426}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)
    * Montreal (`ca-mon`)
    * Toronto (`ca-tor`)
    * Sydney (`au-syd`)


## 03 June 2026
{: #cloud-logs-june0326}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)
    * Montreal (`ca-mon`)
    * Toronto (`ca-tor`)


## 02 June 2026
{: #cloud-logs-june0226}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)
    * Montreal (`ca-mon`)


## 01 June 2026
{: #cloud-logs-june0126}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)
    * Frankfurt (`eu-de`)


## 29 May 2026
{: #cloud-logs-may2926}
{: release-note}

Functional updates and fixes made available on 26 May 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Sao Paulo (`br-sao`)
    * Chennai (`in-che`)


## 26 May 2026
{: #cloud-logs-may2626}
{: release-note}


Functional updates and fixes are available in the Sao Paulo (`br-sao`) region only.

:   New features are included in this release.

    * **Data usage**: The *Data usage* page has been revised and now provides a *User data sent* and a *Metric usage* tab. The *Data usage* page enables you to monitor ingestion trends, identify high-volume logs, and better understand overall data ingestion patterns for improved visibility and analysis.The *User Data Sent* tab provides detailed insights into log and metric ingestion volumes by priority. The *Metric usage* tab provides insights about metric sample distribution by source. For more information, see [About Data Usage](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-data-usage&format=markdown).

    * Enhanced the data usage report that provides an overview of your instance's data usage for the current month, the previous 30 days, or the previous 90 days. For more information, see [Generate Reports](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-data-usage-reports&format=markdown).

    * **Metrics data**: The *Metrics data* page has been revised and now provides a *Usage analysis* and a *Fair usage limits* tab. The *Usage analysis* tab provides comprehensive insights into metrics, metric volumes, metric samples, metric label cardinalities, and time series cardinalities in *Metrics* view, metric labels and metric label variations in *Labels* view, and statistics about executed metric queries in *Queries* view. For example, you can use this tab to identify the label values that contribute most to a metric's cardinality. In addition, you can block ingestion of individual metrics as well as view blocked metrics and unblock them. The *Fair usage limits* tab displays active metric, metric ingestion, and metric query limits for better transparency. For more information, see [Working with the Metrics Data explorer](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-metrics-explorer-r114&format=markdown).

    * Added new visualizations: Introduced Heatmap, Geomap, and Dynamic Widgets for enhanced visualization. For more information, see [Geo widget](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-widget_geo_map&format=markdown), [Heatmap widget](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-widget_heatmap&format=markdown) and [Dynamic widgets](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-widget_dynamic&format=markdown).

    * Improved usability and navigation across the *Parsing Rules* and *Enrichment* pages. For more information, see [Parsing Rules](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-rules_groups&format=markdown) and [Enrichment](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-enrich-howto&format=markdown).



## 20 May 2026
{: #cloud-logs-may2026}
{: release-note}

   API and Terraform support for the Tag retention feature. For more information, see [Configuring archive retention tags to manage data retention](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-retention-tags&format=markdown).


## 18 May 2026
{: #cloud-logs-may1826}
{: release-note}


Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)
    * Sydney (`au-syd`)
    * Sao Paulo (`br-sao`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)
    * Frankfurt (`eu-de`)
    * Osaka (`jp-osa`)
    * Tokyo (`jp-tok`)
    * Toronto (`ca-tor`)
    * Washington, DC (`us-east`)
    * US South (`us-south`)



## 14 May 2026
{: #cloud-logs-may1426}
{: release-note}


Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

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


## 12 May 2026
{: #cloud-logs-may1226}
{: release-note}

Mumbai support
:   The IBM Cloud Logs service is fully supported in the Mumbai (`in-mum`) region.


Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)
    * Sydney (`au-syd`)
    * Sao Paulo (`br-sao`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)
    * Frankfurt (`eu-de`)
    * Osaka (`jp-osa`)
    * Tokyo (`jp-tok`)
    * Toronto (`ca-tor`)


## 11 May 2026
{: #cloud-logs-may1126}
{: release-note}

Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)
    * Sydney (`au-syd`)
    * Sao Paulo (`br-sao`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)
    * Frankfurt (`eu-de`)
    * Osaka (`jp-osa`)
    * Tokyo (`jp-tok`)


## 29 April 2026
{: #cloud-logs-april2926}
{: release-note}

Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)
    * Sydney (`au-syd`)
    * Sao Paulo (`br-sao`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)
    * Frankfurt (`eu-de`)
    * Osaka (`jp-osa`)


## 23 April 2026
{: #cloud-logs-april2326}
{: release-note}

Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)
    * Sydney (`au-syd`)
    * Sao Paulo (`br-sao`)
    * London (`eu-gb`)
    * Madrid (`eu-es`)
    * Frankfurt (`eu-de`)


## 22 April 2026
{: #cloud-logs-april2226}
{: release-note}

Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)
    * Sydney (`au-syd`)
    * Sao Paulo (`br-sao`)
    * Madrid (`eu-es`)
    * Frankfurt (`eu-de`)


## 16 April 2026
{: #cloud-logs-april1626}
{: release-note}

Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)
    * Sydney (`au-syd`)
    * Sao Paulo (`br-sao`)
    * London (`eu-gb`)

## 15 April 2026
{: #cloud-logs-april1526}
{: release-note}

Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)
    * Sydney (`au-syd`)
    * Sao Paulo (`br-sao`)

## 14 April 2026
{: #cloud-logs-april1426}
{: release-note}

Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)
    * Sydney (`au-syd`)


## 13 April 2026
{: #cloud-logs-april1326}
{: release-note}

Functional updates and fixes made available on 09 April 2026 are now available in more regions.

:   Regions supporting new functionality and fixes:

    * Montreal (`ca-mon`)
    * Chennai (`in-che`)

## 09 April 2026
{: #cloud-logs-april0926}
{: release-note}

Release of the Extensions API, CLI and Terraform.
:    For more information, see the [Extensions API](https://cloud.ibm.com/apidocs/logs-service-api#get-extension), [ibm_logs_extension_deployment](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/logs_extension_deployment){: external} and [Managing extensions](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-extensions-mgmt&format=markdown).

Functional updates and fixes are available in the Chennai (`in-che`) region only.

:   New features are included in this release.

    * Pipeline analyzer: You can use the pipeline analyzer to gain full visibility into how your logs are processed before being available for search. You can inspect logs as they move through your data pipelines and gain insights into any parsing rule that a log goes through before it is available for search. For more information, see [Pipeline analyzer](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-pipeline-analyzer&format=markdown).

    * Tag retention: You can use IBM Cloud Object Storage object tags to manage automatically how long log data is available for search in the data bucket. For more information, see [Configuring archive retention tags to manage data retention](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-retention-tags&format=markdown).

    * Schema explorer: You can use the Schema Explorer to automatically detect, highlight, and report on differences detected in the structure of your logs as they are ingested such as duplicate fields with different data types that cause conflict. For more information, see [Schema explorer](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-schema-explorer&format=markdown).

    * TCO updated UI to include configuration of retention tags.

    * Increased the size of the log sample that is included in an alert notification from 1000 characters to 40K characters.

    * Enhanced the *Alert Management* page with options to **Snooze all alerts** or **Snooze selected alerts**.

    * Enhanced the Create Views API to support the creation of views that query data from the IBM Cloud Object Storage data bucket.

    * Enhanced Custom Dashboard with more features like color hashing, and added support to attach Actions from dashboards.

    * Increased the limit to export logs from 2k to 5K in both Priority Insigths and All Logs.

    * Added a new Extension for IBM Cloud Internet Services (CIS). 

    * Metrics Explorer is now available as a drawer that allows to search metrics and labels, explore related metrics, and analyze data by name, label, or value.



## 6 April 2026
{: #cloud-logs-apr0626}
{: release-note}

Release of the Logging agent version 1.8.1
:    For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-apr0626)

## 25 March 2026
{: #cloud-logs-march2526}
{: release-note}

Release of the Extensions API.
:    For more information, see the [Extensions API](https://cloud.ibm.com/apidocs/logs-service-api#get-extension) and [Managing extensions](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-extensions-mgmt&format=markdown).

## 20 February 2026
{: #cloud-logs-feb2026}
{: release-note}

Release of the Logging agent version 1.8.0
:    For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-feb2026)

## 9 Feb 2026
{: #cloud-logs-feb0926}
{: release-note}

Chennai support
:   The IBM Cloud Logs service is fully supported in the Chennai (`in-che`) region.


## 15 December 2025
{: #cloud-logs-dec1525}
{: release-note}

Release of the Logging agent version 1.7.1
:    For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-dec1525)

## 3 December 2025
{: #cloud-logs-dec0325}
{: release-note}

Functional updates and fixes made available on 17 October 2025 are now available in more regions.

:   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](#cloud-logs-oct1725)

## 20 November 2025
{: #cloud-logs-nov2025}
{: release-note}

Functional updates and fixes made available on 17 October 2025 are now available in more regions.

:   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](#cloud-logs-oct1725)


## 13 November 2025
{: #cloud-logs-nov1325}
{: release-note}

Functional updates and fixes made available on 17 October 2025 are now available in more regions.

:   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](#cloud-logs-oct1725)

## 12 November 2025
{: #cloud-logs-nov1225}
{: release-note}

Functional updates and fixes made available on 17 October 2025 are now available in more regions.

:   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](#cloud-logs-oct1725)

## 10 November 2025
{: #cloud-logs-nov1025}
{: release-note}

Functional updates and fixes made available on 17 October 2025 are now available in more regions.

:   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](#cloud-logs-oct1725)

## 6 November 2025
{: #cloud-logs-nov0625}
{: release-note}

Functional updates and fixes made available on 17 October 2025 are now available in more regions.

:   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](#cloud-logs-oct1725)

## 4 November 2025
{: #cloud-logs-nov0425}
{: release-note}

Functional updates and fixes made available on 17 October 2025 are now available in more regions.

:   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](#cloud-logs-oct1725)


## 30 October 2025
{: #cloud-logs-oct3025}

Release of the Logging agent version 1.7.0
:   For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-oct3025)

## 27 October 2025
{: #cloud-logs-oct2725}
{: release-note}

Functional updates and fixes made available on 17 October 2025 are now available in more regions.

:   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](#cloud-logs-oct1725)



## 17 October 2025
{: #cloud-logs-oct1725}
{: release-note}

Functional updates and fixes are available in the Montreal (`ca-mon`) region only.

:   New features are 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](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-new-version-considerations&format=markdown)
       * [Alert priorities](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-priorities&format=markdown)
       * [Terraform changes required to convert alerts](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-migrate_alert_definitions&format=markdown)

    * [Alert] New support for [multi-condition alerts](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-multi-condition&format=markdown).

    * [Alert] New support for [anomaly detection](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-alerts-config-metric&interface=ui&format=markdown#alerts-config-metric-anomaly) in metric alerts.

    * [Reserved Fields](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-reserved-fields&format=markdown) 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](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-enrich-howto&interface=ui&format=markdown#enrich-howto-view) a custom enrichment in the UI and [download](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-enrich-howto&interface=ui&format=markdown#enrich-howto-download) a custom enrichment CSV file to your local system.

    * [UI] [Visual Explorer](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-visual-explorer&format=markdown) 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](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-log-details&format=markdown).

    * [Query] [CLI](docs/cloud-logs?topic=cloud-logs-query-synch&interface=ui) and [API](https://cloud.ibm.com/apidocs/logs-service-api#submit-background-query) support is available for background archive queries (asynchronous archive queries).

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

       * [arrayContains](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-dataprime-ref-array&format=markdown#arrayContains)
       * [inArray](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-dataprime-ref-array&format=markdown#inArray)

    * [Incidents] [**Watch data** now presents undetected values that triggered an alert.](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-incidents&format=markdown#incidents-history) 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](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-query-archive-data-bucket&format=markdown#query_archive) 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.



## 12 September 2025
{: #cloud-logs-sep1225}

Release of the Logging agent version 1.6.3
:   For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-sep1225)

## 26 August 2025
{: #cloud-logs-aug2625}

Release of the Logging agent version 1.6.2
:   For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-aug2625)



## 31 July 2025
{: #cloud-logs-jul3125}

Montreal support
:   The IBM Cloud Logs service is fully supported in the Montreal (`ca-mon`) region.



## 9 July 2025
{: #cloud-logs-jul0925}

Updated Montreal considerations
:   As IBM Cloud provides support for the Montreal (`ca-mon`) region, you need to understand how IBM Cloud Observability services are made available and the actions you need to take to operate in Montreal.


## 26 June 2025
{: #cloud-logs-jun2625}

Release of the Logging agent version 1.6.1
:   For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-jun2625)


## 5 June 2025
{: #cloud-logs-jun0525}

Release of the Logging agent version 1.6.0
:   For more information, see the [Release notes for the Logging agent](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-release-notes-agent&format=markdown#logs-router-agent-jun0525)



## 16 May 2025
{: #cloud-logs-may1625}
{: release-note}


[DataPrime] DataPrime enhancements
:   DataPrime now support the [`multigrouby` operator](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-dataprime-ref-operators&format=markdown#multigroupby).

    DataPrime now supports the [`union` operator](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-dataprime-ref-operators&format=markdown#stitch).

    DataPrime now supports the [`join cross` operator](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-dataprime-ref-operators&format=markdown#join)

    DataPrime now supports passing of query parameter values using [`$p`](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-query-parameters&format=markdown).

[UI] Compact mode
:   [Compact mode](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-compact-views&format=markdown) provides a simplified and streamlined view, enabling users to focus on active monitoring and querying without more widgets, filters, or statistics.

[UI] Shared URL
:   Enhancements added to the [share the URL functionality](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-share_url&format=markdown) so you can share a URL of the the current view of the logs explore screen.

[UI] New extensions
:   New [extensions](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-extensions-mgmt&interface=ui&format=markdown) are available:

    - [Activity Tracking](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-extensions-activity-tracking&format=markdown): Use to get insights into your IBM Cloud activity tracking data.
    - [IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-extensions-kubernetes&format=markdown):  Use to get insights into your IBM Cloud Kubernetes Service logs.
    - [IBM Cloud® Databases for MySQL](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-extensions-db-mysql&format=markdown):  Use to get insights into your IBM Cloud® Databases for MySQL logs.
    - [IBM Cloud® Databases for PostgreSQL](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-extensions-db-postgresql&format=markdown):  Use to get insights into your IBM Cloud® Databases for PostgreSQL logs.

[Custom dashboards] Variable support
:   [Variables](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-variables&format=markdown) 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.


Fixes implemented
:   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.





## 24 February 2025
{: #cloud-logs-feb2425}
{: release-note}

Geo enrichment
:   [Geo enrichment](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-enriching-data&format=markdown#geo-enrichment){: external} now supports ASN (Autonomous System Number). ASN information will be added to the logs when geo enrichment is used.

[DataPrime] DataPrime enhancements
:   DataPrime now support the [`join` operator](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-dataprime-ref-operators&format=markdown#join) types `inner`, `full`, and `left`.

    DataPrime now supports the [`stitch` operator](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-dataprime-ref-operators&format=markdown#stitch).

[UI] Shared URL
:   Support added so you can [share the URL](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-share_url&format=markdown) of the the current view of the logs explore screen.

Fixes implemented
:   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.



## 6 February 2025
{: #cloud-logs-feb0625}
{: release-note}

Context-based restrictions
:  IBM Cloud Logs now supports context-based restrictions (CBR). For more information see, [Protecting resources with context-based restrictions](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-iam-cbr&interface=ui&format=markdown).

## 5 February 2025
{: #cloud-logs-feb0525}
{: release-note}

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?](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-ts-cos-events&format=markdown).

Documentation about using regex for queries
:   Additional information is available about using regex for queries. For more information, see [Using regex when querying data](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-query-regex&format=markdown).

## 12 December 2024
{: #cloud-logs-dec1224}
{: release-note}

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

## 25 November 2024
{: #cloud-logs-nov2524}
{: release-note}

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.

## 6 November 2024
{: #cloud-logs-nov0624}
{: release-note}

Fixes implemented
:   The following issue is resolved.
    - Fixed custom dashboards displaying "Something went wrong" when selecting Analyze and Alert.



## 18 September 2024
{: #cloud-logs-sep1824}
{: release-note}

CSE endpoint support
:   IBM Cloud Logs now supports [CSE endpoints](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-cse_proxy&format=markdown).

## 4 September 2024
{: #cloud-logs-sep0424}
{: release-note}

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](https://cloud.ibm.com/docs/logs-router?format=markdown) to the [IBM Cloud Logs documentation](https://cloud.ibm.com/docs/cloud-logs?format=markdown).

## 29 August 2024
{: #cloud-logs-aug2924}
{: release-note}

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.


## 22 August 2024
{: #cloud-logs-aug2224}
{: release-note}

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.

## 8 August 2024
{: #cloud-logs-aug0824}
{: release-note}

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.

## 30 July 2024
{: #cloud-logs-jul2424}
{: release-note}

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.


## 24 June 2024
{: #cloud-logs-jun2424}
{: release-note}

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](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-getting-started&interface=cli&format=markdown).