From 54b451a11938377c504ad9086b0ad0e6e35ad13e Mon Sep 17 00:00:00 2001 From: Sahidya Date: Wed, 6 Aug 2025 15:23:43 -0400 Subject: [PATCH 1/3] 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 00000000000000..41e87fe66f29ce --- /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/3] 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 41e87fe66f29ce..00000000000000 --- 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 0527d35353acd8e194e5d5b713efc25531d518a6 Mon Sep 17 00:00:00 2001 From: Sahidya Date: Tue, 28 Oct 2025 09:02:05 -0400 Subject: [PATCH 3/3] MS Sentinel connector --- .../logs/2025-10-27-Sentinel-connector.mdx | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 src/content/changelog/logs/2025-10-27-Sentinel-connector.mdx diff --git a/src/content/changelog/logs/2025-10-27-Sentinel-connector.mdx b/src/content/changelog/logs/2025-10-27-Sentinel-connector.mdx new file mode 100644 index 00000000000000..f69575e5708ca1 --- /dev/null +++ b/src/content/changelog/logs/2025-10-27-Sentinel-connector.mdx @@ -0,0 +1,16 @@ +--- +title: "Azure Sentinel Connector" +description: "New Azure Sentinel Connector based on Codeless Connector Framework (CCF)" +date: "2025-10-27" +--- + +Logpush now supports integration with [Microsoft Sentinel](https://www.microsoft.com/en-us/security/business/siem-and-xdr/microsoft-sentinel).The new Azure Sentinel Connector built on Microsoft’s Codeless Connector Framework (CCF), is now avaialble. This solution replaces the previous Azure Functions-based connector, offering significant improvements in security, data control, and ease of use for customers. Logpush customers can send logs to Azure Blob Storage and configure this new Sentinel Connector to ingest those logs directly into Microsoft Sentinel. + +This upgrade significantly streamlines log ingestion, improves security, and provides greater control: + +- Simplified Implementation: Easier for engineering teams to set up and maintain. +- Cost Control: New support for Data Collection Rules (DCRs) allows you to filter and transform logs at ingestion time, offering potential cost savings. +- Enhanced Security: CCF provides a higher level of security compared to the older Azure Functions connector. +- ata Lake Integration: Includes native integration with Data Lake. + +Find the new solution [here](https://marketplace.microsoft.com/en-us/product/azure-application/cloudflare.azure-sentinel-solution-cloudflare-ccf?tab=Overview) and refer to the [Cloudflare's developer documention](https://developers.cloudflare.com/analytics/analytics-integrations/sentinel/#supported-logs:~:text=WorkBook%20fields,-Analytic%20rules)for more information on the connector, including setup steps, supported logs and Microsfot's resources.