From 54b451a11938377c504ad9086b0ad0e6e35ad13e Mon Sep 17 00:00:00 2001 From: Sahidya Date: Wed, 6 Aug 2025 15:23:43 -0400 Subject: [PATCH 1/4] sahidya/ibm_cloud_logs --- .../logs/2025-08-06-IBM-cloud-logs-integration.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 src/content/changelog/logs/2025-08-06-IBM-cloud-logs-integration.mdx diff --git a/src/content/changelog/logs/2025-08-06-IBM-cloud-logs-integration.mdx b/src/content/changelog/logs/2025-08-06-IBM-cloud-logs-integration.mdx new file mode 100644 index 000000000000000..41e87fe66f29ceb --- /dev/null +++ b/src/content/changelog/logs/2025-08-06-IBM-cloud-logs-integration.mdx @@ -0,0 +1,11 @@ +--- +title: IBM Cloud Logs as Logpush destination +description: Enable IBM Cloud Logs as a Logpush destination +date: 2025-08-06 +--- + +Cloudflare Logpush now supports IBM Cloud Logs as a native destination. + +Logs from Cloudflare can be sent to [IBM Cloud Logs](https://www.ibm.com/products/cloud-logs) via [Logpush](/logs/logpush/). The setup can be done through the Logpush UI in the Cloudflare Dashboard or by using the [Logpush API](/api/resources/logpush/subresources/jobs/). The integration requires IBM Cloud Logs HTTP Source Address and an IBM API Key. The feature also allows for filtering events and selecting specific log fields. + +For more information refer to [Destination Configuration](/logs/logpush/logpush-job/enable-destinations/ibm-cloud-logs/) documentation. From ec000cb804ff95bf445ea1fa408729de3314c678 Mon Sep 17 00:00:00 2001 From: Sahidya Date: Wed, 13 Aug 2025 15:41:18 -0400 Subject: [PATCH 2/4] Delete 2025-08-06-IBM-cloud-logs-integration.mdx --- .../logs/2025-08-06-IBM-cloud-logs-integration.mdx | 11 ----------- 1 file changed, 11 deletions(-) delete mode 100644 src/content/changelog/logs/2025-08-06-IBM-cloud-logs-integration.mdx diff --git a/src/content/changelog/logs/2025-08-06-IBM-cloud-logs-integration.mdx b/src/content/changelog/logs/2025-08-06-IBM-cloud-logs-integration.mdx deleted file mode 100644 index 41e87fe66f29ceb..000000000000000 --- a/src/content/changelog/logs/2025-08-06-IBM-cloud-logs-integration.mdx +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: IBM Cloud Logs as Logpush destination -description: Enable IBM Cloud Logs as a Logpush destination -date: 2025-08-06 ---- - -Cloudflare Logpush now supports IBM Cloud Logs as a native destination. - -Logs from Cloudflare can be sent to [IBM Cloud Logs](https://www.ibm.com/products/cloud-logs) via [Logpush](/logs/logpush/). The setup can be done through the Logpush UI in the Cloudflare Dashboard or by using the [Logpush API](/api/resources/logpush/subresources/jobs/). The integration requires IBM Cloud Logs HTTP Source Address and an IBM API Key. The feature also allows for filtering events and selecting specific log fields. - -For more information refer to [Destination Configuration](/logs/logpush/logpush-job/enable-destinations/ibm-cloud-logs/) documentation. From e441d0d61aa5b249276e1d3cf19c034ab753f32c Mon Sep 17 00:00:00 2001 From: Sahidya Date: Fri, 22 Aug 2025 15:54:58 -0400 Subject: [PATCH 3/4] dedicated-egress-ip-logpush --- .../2025-08-22-dedicated-egress-ip-logpush.mdx | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx diff --git a/src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx b/src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx new file mode 100644 index 000000000000000..066c519e77eed27 --- /dev/null +++ b/src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx @@ -0,0 +1,15 @@ +--- +title: "Dedicated Egress IP for Logpush" +description: "Set up dedicated egress IPs for Logpush using Aegis IPs" +date: "2025-08-22" +--- + +Cloudflare Logpush can now deliver logs from using fixed, dedicated egress IPs. By routing Logpush traffic through a Cloudflare zone enabled with [Aegis IP](/aegis/), your log destination only needs to allow Aegis IPs making setup more secure. + +Highlights: + +- Fixed egress IPs ensure your destination only accepts traffic from known addresses. +- Works with any supported Logpush destination. +- Recommended to use a dedicated zone as a proxy for easier management. + +To get started, work with your Cloudflare account team to provision Aegis IPs, then configure your Logpush job to deliver logs through the proxy zone. For full setup instructions, see the [documentation](/logs/logpush/logpush-job/enable-destinations/egress-ip/). From 12a34b7843e336354232f39a9062861771c3339f Mon Sep 17 00:00:00 2001 From: Sahidya Date: Fri, 22 Aug 2025 16:29:56 -0400 Subject: [PATCH 4/4] Update src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx Co-authored-by: Patricia Santa Ana <103445940+patriciasantaana@users.noreply.github.com> --- .../changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx b/src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx index 066c519e77eed27..80195fa1cae5c34 100644 --- a/src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx +++ b/src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx @@ -12,4 +12,4 @@ Highlights: - Works with any supported Logpush destination. - Recommended to use a dedicated zone as a proxy for easier management. -To get started, work with your Cloudflare account team to provision Aegis IPs, then configure your Logpush job to deliver logs through the proxy zone. For full setup instructions, see the [documentation](/logs/logpush/logpush-job/enable-destinations/egress-ip/). +To get started, work with your Cloudflare account team to provision Aegis IPs, then configure your Logpush job to deliver logs through the proxy zone. For full setup instructions, refer to the [Logpush documentation](/logs/logpush/logpush-job/enable-destinations/egress-ip/).