diff --git a/public/__redirects b/public/__redirects index 0795a1711c9f07..7a11fa395a0e01 100644 --- a/public/__redirects +++ b/public/__redirects @@ -983,6 +983,7 @@ /logs/reference/custom-fields/ /logs/logpush/logpush-job/custom-fields/ 301 /logs/get-started/api-configuration/ /logs/logpush/logpush-job/api-configuration/ 301 /logs/get-started/permissions/ /logs/logpush/permissions/ 301 +/logs/get-started/ /logs/logpush/ 301 # magic-firewall /magic-firewall/reference/examples/ /magic-firewall/how-to/add-rules/ 301 diff --git a/src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx b/src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx index e9970f541fec35..7e29cfc5bd5f29 100644 --- a/src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx +++ b/src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx @@ -25,4 +25,4 @@ User Actions available: - **Downloads & Uploads** - **Printing** -Learn more about how to get started with Logpush in our [documentation](/logs/get-started/). +Learn more about how to get started with Logpush in our [documentation](/logs/logpush/). diff --git a/src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx b/src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx index cda9cdfafce7a0..630416c841fb46 100644 --- a/src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx +++ b/src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx @@ -4,7 +4,7 @@ description: Seamlessly configure Logpush to R2 in just one click. date: 2025-03-06 --- -We’ve streamlined the [Logpush](/logs/get-started/) setup process by integrating R2 bucket creation directly into the Logpush workflow! +We’ve streamlined the [Logpush](/logs/logpush/) setup process by integrating R2 bucket creation directly into the Logpush workflow! Now, you no longer need to navigate multiple pages to manually create an R2 bucket or copy credentials. With this update, you can seamlessly **configure a Logpush job to R2 in just one click**, reducing friction and making setup faster and easier. diff --git a/src/content/docs/ai-gateway/observability/logging/logpush.mdx b/src/content/docs/ai-gateway/observability/logging/logpush.mdx index e79a69aef16144..e9cb672433b8f3 100644 --- a/src/content/docs/ai-gateway/observability/logging/logpush.mdx +++ b/src/content/docs/ai-gateway/observability/logging/logpush.mdx @@ -89,7 +89,7 @@ Once you have generated the key pair, upload the public key to your AI Gateway s ## 3. Set up Logpush -To set up Logpush, refer to [Logpush Get Started](/logs/get-started/). +To set up Logpush, refer to [Logpush](/logs/logpush/) documentation. ## 4. Receive encrypted logs diff --git a/src/content/docs/cloudflare-one/tutorials/ai-wrapper-tenant-control.mdx b/src/content/docs/cloudflare-one/tutorials/ai-wrapper-tenant-control.mdx index 0f57a97eea16e8..1bf7bfc5c857c7 100644 --- a/src/content/docs/cloudflare-one/tutorials/ai-wrapper-tenant-control.mdx +++ b/src/content/docs/cloudflare-one/tutorials/ai-wrapper-tenant-control.mdx @@ -474,7 +474,7 @@ Organizations that adopt Cloudflare to secure access to AI agents will benefit f Zero Trust will log all [Access events](/cloudflare-one/insights/logs/audit-logs/) and [DLP detections](/cloudflare-one/insights/logs/gateway-logs/#http-logs). In addition, AI Gateway provides [visibility](/ai-gateway/observability/logging/) into user prompts, model response, token usage, and costs. -Logs can be exported to external providers with [Logpush](/logs/get-started/). +Logs can be exported to external providers with [Logpush](/logs/logpush/). ### Configurability diff --git a/src/content/docs/dns/additional-options/analytics.mdx b/src/content/docs/dns/additional-options/analytics.mdx index 04133b6ec87985..489829610bc1d8 100644 --- a/src/content/docs/dns/additional-options/analytics.mdx +++ b/src/content/docs/dns/additional-options/analytics.mdx @@ -124,4 +124,4 @@ query GetTotalDNSQueryCount { Logs let Enterprise customers view [detailed information](/logs/reference/log-fields/zone/dns_logs/) about individual DNS queries. -For help setting up Logpush, refer to [Get started with Logs](/logs/get-started/). \ No newline at end of file +For help setting up Logpush, refer to [Logpush](/logs/logpush/) documentation. \ No newline at end of file diff --git a/src/content/docs/dns/internal-dns/analytics.mdx b/src/content/docs/dns/internal-dns/analytics.mdx index 004a957715fe44..b3c1bdd560b50a 100644 --- a/src/content/docs/dns/internal-dns/analytics.mdx +++ b/src/content/docs/dns/internal-dns/analytics.mdx @@ -20,6 +20,6 @@ The [fields](/analytics/graphql-api/getting-started/querying-basics/) added to c ## Logs -Leverage Logpush jobs for [Gateway DNS](/logs/reference/log-fields/account/gateway_dns/#internaldnsfallbackstrategy). For help setting up Logpush, refer to [Get started with Logs](/logs/get-started/). +Leverage Logpush jobs for [Gateway DNS](/logs/reference/log-fields/account/gateway_dns/#internaldnsfallbackstrategy). For help setting up Logpush, refer to [Logpush](/logs/logpush/) documentation. You can also set up [Logpush filters](/logs/logpush/logpush-job/filters/) to only push logs related to a specific [internal zone](/dns/internal-dns/internal-zones/) or [view](/dns/internal-dns/dns-views/) ID. \ No newline at end of file diff --git a/src/content/docs/logs/get-started/index.mdx b/src/content/docs/logs/get-started/index.mdx deleted file mode 100644 index 13f67ab993be7e..00000000000000 --- a/src/content/docs/logs/get-started/index.mdx +++ /dev/null @@ -1,15 +0,0 @@ ---- -pcx_content_type: navigation -title: Get started -sidebar: - order: 42 - ---- - -import { LinkButton } from "~/components" - -Cloudflare Logpush supports pushing logs to storage services, SIEMs, and log management providers via the Cloudflare dashboard or API. - -Cloudflare aims to support additional services in the future. Interested in a particular service? Take this [survey](https://goo.gl/forms/0KpMfae63WMPjBmD2). - - Enable destinations diff --git a/src/content/docs/logs/index.mdx b/src/content/docs/logs/index.mdx index bed08c6d9c726b..df566a00e5346d 100644 --- a/src/content/docs/logs/index.mdx +++ b/src/content/docs/logs/index.mdx @@ -22,7 +22,7 @@ These logs are helpful for debugging, identifying configuration adjustments, and ## Features - + Push your request or event logs to your cloud service provider using Logpush, which can be configured via the Cloudflare dashboard or API. diff --git a/src/content/docs/logs/logpush/index.mdx b/src/content/docs/logs/logpush/index.mdx index c54fcd2a2909fc..f5f536cdbd6d0f 100644 --- a/src/content/docs/logs/logpush/index.mdx +++ b/src/content/docs/logs/logpush/index.mdx @@ -12,6 +12,10 @@ Logpush delivers logs in batches as quickly as possible, with no minimum batch s Logpush does not offer storage or search functionality for logs; its primary aim is to send logs as quickly as they arrive. +Cloudflare Logpush supports pushing logs to storage services, SIEMs, and log management providers via the Cloudflare dashboard or API. + +Cloudflare aims to support additional services in the future. Interested in a particular service? Take this [survey](https://goo.gl/forms/0KpMfae63WMPjBmD2). + ## Limits There is currently a max limit of **4 Logpush jobs per zone**. Trying to create a job once the limit has been reached will result in an error message: `creating a new job is not allowed: exceeded max jobs allowed`. diff --git a/src/content/docs/logs/logpush/logpush-job/enable-destinations/s3-compatible-endpoints.mdx b/src/content/docs/logs/logpush/logpush-job/enable-destinations/s3-compatible-endpoints.mdx index ad77054ac2a0c1..59f294b8ad8ce1 100644 --- a/src/content/docs/logs/logpush/logpush-job/enable-destinations/s3-compatible-endpoints.mdx +++ b/src/content/docs/logs/logpush/logpush-job/enable-destinations/s3-compatible-endpoints.mdx @@ -22,7 +22,7 @@ Cloudflare Logpush supports pushing logs to S3-compatible destinations via the C * [Oracle Cloud Object Storage](https://docs.cloud.oracle.com/en-us/iaas/Content/Object/Tasks/s3compatibleapi.htm) * On-premise [Ceph Object Gateway](https://docs.ceph.com/en/latest/radosgw/s3/) -For more information about Logpush and the current production APIs, refer to [Cloudflare Logpush](/logs/get-started/) documentation. +For more information about Logpush and the current production APIs, refer to [Cloudflare Logpush](/logs/logpush/) documentation. ## Manage via the Cloudflare dashboard diff --git a/src/content/docs/logs/reference/index.mdx b/src/content/docs/logs/reference/index.mdx index 700f96a874d62b..da92f6c26993f3 100644 --- a/src/content/docs/logs/reference/index.mdx +++ b/src/content/docs/logs/reference/index.mdx @@ -2,7 +2,7 @@ pcx_content_type: navigation title: Reference sidebar: - order: 111 + order: 124 --- diff --git a/src/content/docs/page-shield/policies/violations.mdx b/src/content/docs/page-shield/policies/violations.mdx index b8b76a3aa95641..53c8263649cb84 100644 --- a/src/content/docs/page-shield/policies/violations.mdx +++ b/src/content/docs/page-shield/policies/violations.mdx @@ -132,4 +132,4 @@ https://api.cloudflare.com/client/v4/graphql \ Information about policy violations is available in the [`page_shield_events` dataset](/logs/reference/log-fields/zone/page_shield_events/). -For more information on configuring Logpush jobs, refer to [Logs: Get started](/logs/get-started/). +For more information on configuring Logpush jobs, refer to [Logpush](/logs/logpush/) documentation. diff --git a/src/content/docs/reference-architecture/design-guides/network-vpn-migration.mdx b/src/content/docs/reference-architecture/design-guides/network-vpn-migration.mdx index 5594d1bd163e4e..0e96b99379e726 100644 --- a/src/content/docs/reference-architecture/design-guides/network-vpn-migration.mdx +++ b/src/content/docs/reference-architecture/design-guides/network-vpn-migration.mdx @@ -164,7 +164,7 @@ As steps are taken in this first phase and the first users will start accessing - Monitoring for potential threats by a SOC, possibly using a security information and event management ([SIEM](https://www.cloudflare.com/learning/security/what-is-siem/)) service. - Visibility into application traffic to see where potential security and performance improvements can be made (see also phase 2). -Cloudflare provides visibility at different levels, available through the dashboard or exported using [Logpush](/logs/get-started/). For traffic flowing over Magic WAN IPsec tunnels, [Network Analytics](/analytics/network-analytics/) can be found in the dashboard and through the [GraphQL API](/analytics/graphql-api/). This will show sampled statistics of the traffic and can be used for trend and traffic flow analysis. +Cloudflare provides visibility at different levels, available through the dashboard or exported using [Logpush](/logs/logpush/). For traffic flowing over Magic WAN IPsec tunnels, [Network Analytics](/analytics/network-analytics/) can be found in the dashboard and through the [GraphQL API](/analytics/graphql-api/). This will show sampled statistics of the traffic and can be used for trend and traffic flow analysis. Next are more detailed [network session logs](/logs/reference/log-fields/account/zero_trust_network_sessions/) that collect information on all network connections/sessions going through Cloudflare's secure web gateway, including unsuccessful requests. These are followed by [Gateway activity logs](/cloudflare-one/insights/logs/gateway-logs/), which contain information about triggered policies as traffic gets inspected by the gateway engine. A combination of these logs will enable full visibility into all network flows, including users' identities. Using this information, network and security teams can run their analysis on what type of traffic flows where, and use that to plan for the next steps. diff --git a/src/content/docs/zaraz/advanced/logpush.mdx b/src/content/docs/zaraz/advanced/logpush.mdx index 98acb00bb6cac3..623d61c0c42909 100644 --- a/src/content/docs/zaraz/advanced/logpush.mdx +++ b/src/content/docs/zaraz/advanced/logpush.mdx @@ -21,7 +21,7 @@ Navigate to your Website (Zone) and from the left sidebar find **Analytics and L Under this **Analytics and Logs** section navigate to **Logpush** -Click on **Create a Logpush Job** and follow the steps described in the [Logpush documentation](/logs/get-started/). +Click on **Create a Logpush Job** and follow the steps described in the [Logpush](/logs/logpush/) documentation. When it comes to selecting a dataset please make sure to select **Zaraz Events**