Skip to content

Logs restructure and new filtering docs#29199

Closed
cloudflare-noelle wants to merge 4 commits intocloudflare:productionfrom
cloudflare-noelle:logs-restructure-docs
Closed

Logs restructure and new filtering docs#29199
cloudflare-noelle wants to merge 4 commits intocloudflare:productionfrom
cloudflare-noelle:logs-restructure-docs

Conversation

@cloudflare-noelle
Copy link
Copy Markdown
Contributor

Summary

Screenshots (optional)

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

- Create dashboard-logs/ folder for UI-accessible logs
  - Add admin-activity-logs.mdx (new page)
  - Add ssh-command-logs.mdx (new page)
  - Move access-authentication-logs.mdx (renamed from audit-logs.mdx)
  - Move gateway-logs/ folder with index.mdx and manage-pii.mdx
  - Move scim-logs.mdx
  - Move posture-logs.mdx
  - Move tunnel-audit-logs.mdx

- Create logpush/ folder for Logpush-related documentation
  - Move logpush.mdx content to index.mdx
  - Move enable-logs.mdx to email-security-logs.mdx
  - Move use-logpush-with-ids.mdx to ids-logs.mdx
  - Rename filter-views.mdx to network-firewall-log-filters.mdx

- Preserve existing overview content (Log Retention, Log Explorer, CMB, Data Privacy)
- Add beta-flagged 'Log viewer' section to access-authentication-logs.mdx
- Add beta-flagged 'Log viewer' section to gateway-logs/index.mdx
- Document new capabilities: field filtering, column customization,
  timestamp details view, and classic UI toggle

import { DirectoryListing } from "~/components";

The following logs are available in the [Zero Trust dashboard](https://one.dash.cloudflare.com/). Go to **Insights** > **Logs** to view activity for your organization.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tunnel audit logs are located in the coredash, not Cloudflare One. The content fits under "Dashboard logs", but technically the Insights > Logs part doesn't apply. Should "Dashboard logs" only include CF1 dashlogs, or should we remove the Insights > Logs instructions from this page?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm good point. I think removing the instructions in the dashboard makes the most sense. The Tunnel Audit log docs were here already, so I want trying to find a place to move them and be organized.


import { GlossaryTooltip, TabItem, Tabs, APIRequest } from "~/components";
import { GlossaryTooltip, TabItem, Tabs, APIRequest, InlineBadge } from "~/components";

Copy link
Copy Markdown
Contributor

@ranbel ranbel Mar 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommend starting page with an introductory paragraph instead of a header. Perhaps expand on the existing intro: https://developers.cloudflare.com/cloudflare-one/insights/logs/audit-logs/


## Log viewer <InlineBadge preset="beta" />

Gateway activity logs use an updated log viewer with the following capabilities:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommend moving the log viewer further down the page. Start the page with an overview of what Gateway activity logs are and where to find them.

- **View details** - Select a timestamp to view the full details of a log entry.
- **Switch to classic view** - Select **Use old UI** to return to the previous log viewer.

## Overview
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

accidentally duplicated overview section?

@@ -39,24 +37,24 @@ For more information on supported destinations, refer to [Enable destinations](/

## Zero Trust datasets
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we change this to "Cloudflare One data sets" and add Email security, IDS, and Network Firewall to this table?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not opposed, I'm not entirely sure of all the logic that went into the log documentation up until now, mostly have just been trying to clean it up with the launch of the new logs UI. Want to merge the current commit and we can continue to clean it up and add?

…gs index

The 'Go to Insights > Logs' instruction doesn't apply to all logs in this
section (e.g., Tunnel audit logs are in the account dashboard). Removed
the specific navigation path to avoid confusion.
- Remove navigation instructions from dashboard-logs/index.mdx
  (doesn't apply to all logs like Tunnel audit logs)
- Replace 'Log viewer' header with introductory paragraph in
  access-authentication-logs.mdx
- Reorganize gateway-logs/index.mdx to start with overview of what
  Gateway activity logs are and where to find them, then move log
  viewer section further down the page
@cloudflare-noelle
Copy link
Copy Markdown
Contributor Author

@ranbel I think I addressed everything, let me know if I missed anything

@ranbel
Copy link
Copy Markdown
Contributor

ranbel commented Mar 31, 2026

edited version: #29501

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants