From f6c90e209731e1c339878e18cfab1c7c813abcfa Mon Sep 17 00:00:00 2001 From: Amit Nakod Date: Mon, 9 Feb 2026 12:39:03 +0530 Subject: [PATCH 1/2] in-che region details in doc --- endpoints_api.md | 3 +++ endpoints_ingress.md | 2 ++ ips4firewalls.md | 4 ++++ regions.md | 1 + 4 files changed, 10 insertions(+) diff --git a/endpoints_api.md b/endpoints_api.md index fc8bf79..691d968 100644 --- a/endpoints_api.md +++ b/endpoints_api.md @@ -34,6 +34,8 @@ Public endpoints can be accessed from the public internet. | Asia Pacific | Sydney (`au-syd`) | `dashboard.au-syd.logs.cloud.ibm.com/` | Access to the dashboard | | Asia Pacific | Tokyo (`jp-tok`) | `.api.jp-tok.logs.cloud.ibm.com` | Query logs and manage the instance | | Asia Pacific | Tokyo (`jp-tok`) | `dashboard.jp-tok.logs.cloud.ibm.com/` | Access to the dashboard | +| Asia Pacific | Chennai (`in-che`) | `.api.in-che.logs.cloud.ibm.com` | Query logs and manage the instance | +| Asia Pacific | chennai (`in-che`) | `dashboard.in-che.logs.cloud.ibm.com/` | Access to the dashboard | | Europe | Frankfurt (`eu-de`) | `.api.eu-de.logs.cloud.ibm.com` | Query logs and manage the instance | | Europe | Frankfurt (`eu-de`) | `dashboard.eu-de.logs.cloud.ibm.com/` | Access to the dashboard | | Europe | London (`eu-gb`) | `.api.eu-gb.logs.cloud.ibm.com` | Query logs and manage the instance | @@ -64,6 +66,7 @@ Private endpoints restrict access to the {{site.data.keyword.cloud_notm}} privat | Asia Pacific | Osaka (`jp-osa`) | `.api.private.jp-osa.logs.cloud.ibm.com` | Query logs and manage the instance | | Asia Pacific | Sydney (`au-syd`) | `.api.private.au-syd.logs.cloud.ibm.com` | Query logs and manage the instance | | Asia Pacific | Tokyo (`jp-tok`) | `.api.private.jp-tok.logs.cloud.ibm.com` | Query logs and manage the instance | +| Asia Pacific | Chennai (`in-che`) | `.api.private.in-che.logs.cloud.ibm.com` | Query logs and manage the instance | | Europe | Frankfurt (`eu-de`) | `.api.private.eu-de.logs.cloud.ibm.com` | Query logs and manage the instance | | Europe | London (`eu-gb`) | `.api.private.eu-gb.logs.cloud.ibm.com` | Query logs and manage the instance | | Europe | Madrid (`eu-es`) | `.api.private.eu-es.logs.cloud.ibm.com` | Query logs and manage the instance | diff --git a/endpoints_ingress.md b/endpoints_ingress.md index d9f7b6e..4e27cab 100644 --- a/endpoints_ingress.md +++ b/endpoints_ingress.md @@ -31,6 +31,7 @@ Public endpoints can be accessed from the public internet. | Asia Pacific | Osaka (`jp-osa`) | `.ingress.jp-osa.logs.cloud.ibm.com` | | Asia Pacific | Sydney (`au-syd`) | `.ingress.au-syd.logs.cloud.ibm.com` | | Asia Pacific | Tokyo (`jp-tok`) | `.ingress.jp-tok.logs.cloud.ibm.com` | +| Asia Pacific | Chennai (`in-che`) | `.ingress.in-che.logs.cloud.ibm.com` | | Europe | Frankfurt (`eu-de`) | `.ingress.eu-de.logs.cloud.ibm.com` | | Europe | London (`eu-gb`) | `.ingress.eu-gb.logs.cloud.ibm.com` | | Europe | Madrid (`eu-es`) | `.ingress.eu-es.logs.cloud.ibm.com` | @@ -51,6 +52,7 @@ Private endpoints restrict access to the {{site.data.keyword.cloud_notm}} privat | Asia Pacific | Osaka (`jp-osa`) | `.ingress.private.jp-osa.logs.cloud.ibm.com` | | Asia Pacific | Sydney (`au-syd`) | `.ingress.private.au-syd.logs.cloud.ibm.com` | | Asia Pacific | Tokyo (`jp-tok`) | `.ingress.private.jp-tok.logs.cloud.ibm.com` | +| Asia Pacific | Chennai (`in-che`) | `.ingress.private.in-che.logs.cloud.ibm.com` | | Europe | Frankfurt (`eu-de`) | `.ingress.private.eu-de.logs.cloud.ibm.com` | | Europe | London (`eu-gb`) | `.ingress.private.eu-gb.logs.cloud.ibm.com` | | Europe | Madrid (`eu-es`) | `.ingress.private.eu-es.logs.cloud.ibm.com` | diff --git a/ips4firewalls.md b/ips4firewalls.md index b8e1dd2..06a0fd1 100644 --- a/ips4firewalls.md +++ b/ips4firewalls.md @@ -40,6 +40,7 @@ These private IP addresses are used to archive logs to {{site.data.keyword.cos_f | Sao Paulo (`br-sao`) | 10.12.178.24 \n 10.12.79.160 \n 10.51.193.140 | | Sydney (`au-syd`) | 10.223.237.71 \n 10.223.243.160 \n 10.223.254.90 | | Tokyo (`jp-tok`) | 10.223.197.221 \n 10.223.208.108 \n 10.223.220.15 | +| Chennai (`in-che`) | 10.46.129.80 \n 10.46.133.80 \n 10.46.137.80 | | Toronto (`ca-tor`) | 10.223.153.79 \n 10.223.168.204 \n 10.223.176.163 | | Washington, DC (`us-east`) | 10.22.41.104 \n 10.22.53.64 \n 10.22.56.46 | {: caption="Private IP addresses for {{site.data.keyword.cos_full_notm}}, {{site.data.keyword.en_short}} and {{site.data.keyword.messagehub}}" caption-side="top"} @@ -60,6 +61,7 @@ These public IP addresses are used to send events to {{site.data.keyword.en_full | Sao Paulo (`br-sao`) | 13.116.82.31 \n 163.107.85.232 \n 163.109.87.9 | | Sydney (`au-syd`) | 159.23.94.217 \n 130.198.9.241 \n 135.90.138.121 | | Tokyo (`jp-tok`) | 162.133.137.8 \n 128.168.136.18 \n 165.192.138.249 | +| Chennai (`in-che`) | 169.38.15.172 \n 169.38.18.136 \n 169.38.9.71 | | Toronto (`ca-tor`) | 163.66.94.68 \n 163.74.88.241 \n 163.74.88.241 | | Washington, DC (`us-east`) | 150.239.81.194 \n 169.63.190.140 \n 150.239.222.67 | {: caption="Public IP addresses for {{site.data.keyword.en_short}} and {{site.data.keyword.messagehub}}" caption-side="top"} @@ -84,6 +86,7 @@ These are private ingress endpoints IP addresses for {{site.data.keyword.logs_fu | Sao Paulo (`br-sao`) | 166.9.246.86 \n 166.9.246.118 \n 166.9.246.142 | | Sydney (`au-syd`) | 166.9.244.118 \n 166.9.244.150 \n 166.9.244.182 | | Tokyo (`jp-tok`) | 166.9.249.125 \n 166.9.249.154 \n 166.9.249.190 | +| Chennai (`in-che`) | 166.9.236.7 | | Toronto (`ca-tor`) | 166.9.209.7 \n 166.9.247.184 \n 166.9.247.221 | | Washington, DC (`us-east`) | 166.9.231.251 \n 166.9.251.88 \n 166.9.233.27 | {: caption="IP addresses for {{site.data.keyword.logs_full_notm}} private ingress endpoints" caption-side="top"} @@ -108,6 +111,7 @@ These are the private API IP addresses used for {{site.data.keyword.logs_full_no | Sao Paulo (`br-sao`) | 166.9.246.85 \n 166.9.246.117 \n 166.9.246.141 | | Sydney (`au-syd`) | 166.9.244.117 \n 166.9.244.149 \n 166.9.244.181 | | Tokyo (`jp-tok`) | 166.9.249.126 \n 166.9.249.155 \n 166.9.249.164 | +| Chennai (`in-che`) | 166.9.236.6 | | Toronto (`ca-tor`) | 166.9.209.6 \n 166.9.209.34 \n 166.9.247.202 | | Washington, DC (`us-east`) | 166.9.231.250 \n 166.9.251.87 \n 166.9.233.26 | {: caption="{{site.data.keyword.logs_full_notm}} private API IP addresses" caption-side="top"} diff --git a/regions.md b/regions.md index 5eb847c..8c1ede7 100644 --- a/regions.md +++ b/regions.md @@ -34,6 +34,7 @@ The following table lists the locations where the service is available: | Asia Pacific | Osaka (`jp-osa`) | Not applicable | `MZR` | | Asia Pacific | Sydney (`au-syd`) | Not applicable | `MZR` | | Asia Pacific | Tokyo (`jp-tok`) | Not applicable | `MZR` | +| Asia Pacific | Chennai (`in-che`) | Not applicable | `MZR` | | Europe | Frankfurt (`eu-de`) `(*)` | YES | `MZR` | | Europe | London (`eu-gb`) | NO | `MZR` | | Europe | Madrid (`eu-es`) `(*)` | YES | `MZR` | From 9aa34a3bd93131cfc7f92f2a73082e6f9dae442a Mon Sep 17 00:00:00 2001 From: sony neyyan Date: Wed, 11 Feb 2026 17:28:41 +0530 Subject: [PATCH 2/2] Additional changes for PR #25 Chennai MZR docs --- release-notes.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/release-notes.md b/release-notes.md index 7f0fce2..e2d9f42 100644 --- a/release-notes.md +++ b/release-notes.md @@ -20,7 +20,11 @@ content-type: release-note Use these release notes to learn about the latest updates to {{site.data.keyword.logs_full}}. {: shortdesc} +## 9 February 2026 +{: #cloud-logs-feb0926} +Chennai support +: The {{site.data.keyword.logs_full_notm}} service is fully supported in the Chennai (`in-che`) region. ## 15 December 2025 {: #cloud-logs-dec1525}