Skip to content

Commit 834598e

Browse files
committed
Add Log Explorer callout section
1 parent c336637 commit 834598e

File tree

1 file changed

+5
-1
lines changed
  • src/content/docs/cloudflare-one/insights/logs

1 file changed

+5
-1
lines changed

src/content/docs/cloudflare-one/insights/logs/index.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ head:
88
content: Zero Trust logs
99
---
1010

11-
import { DirectoryListing } from "~/components";
11+
import { DirectoryListing, Badge } from "~/components";
1212

1313
Review detailed logs for your Zero Trust organization.
1414

@@ -30,6 +30,10 @@ Cloudflare Zero Trust logs are stored for a varying period of time based on the
3030

3131
[^1]: Enterprise users on per query plans cannot store DNS logs via Cloudflare. You can still export logs via [Logpush](/cloudflare-one/insights/logs/logpush/). For more information, contact your account team.
3232

33+
## Log Explorer <Badge text="Beta" variant="caution" size="small" />
34+
35+
Log Explorer users can store Zero Trust logs directly within Cloudflare in an [R2 bucket](/r2/) and access them with the dashboard or API. For more information, refer to [Log Explorer](/logs/log-explorer/).
36+
3337
## Customer Metadata Boundary
3438

3539
Cloudflare Zero Trust can be used with the Data Localization Suite to ensure that data storage is restricted to a specific geographic region. For more information refer to [Customer Metadata Boundary](/data-localization/metadata-boundary/).

0 commit comments

Comments
 (0)