Sahidya

This commit **updates the documentation for Audit Logs v2** to reflect its **General Availability (GA)** status. The `src/content/docs/fundamentals/account/account-security/audit-logs.mdx` file has been revised to remove all beta references, clarify product coverage, and include important details regarding log retention policies. This **documentation update** ensures users have accurate and up-to-date information on the fully released **Audit Logs feature**, enhancing clarity and user understanding of its capabilities and operational aspects.

This commit **adds a new changelog entry** to announce the **General Availability (GA) of Audit Logs v2**. It introduces a new documentation file, `src/content/changelog/audit-logs/2026-03-10-audit-logs-v2-ga.mdx`, which details the features, access methods, and important notes for this updated auditing capability. This **documentation update** serves as a crucial **release announcement**, informing users about the official launch and capabilities of the enhanced **Audit Logs** system.

This commit introduces **SentinelOne as a new Logpush destination**, enabling users to forward their logs directly to the SentinelOne platform for enhanced security monitoring and data analysis. This **new capability** expands the existing **Logpush feature** by providing an additional integration option for log forwarding. The change includes an update to the **changelog** (`src/content/changelog/logs/2025-12-11-sentinelone-destination.mdx`) to officially announce this integration.

This commit **adds a new changelog entry** to `src/content/changelog/logs/2025-11-11-health-dashboards.mdx`, serving as a **documentation update** for the project. It formally introduces the new **Logpush Health Dashboards** feature, detailing its functionality and how users can access it. This **enhances user awareness** by providing essential information about a significant new capability, ensuring users are informed about the latest monitoring tools available within the Logpush system.

This commit provides a **documentation update** by correcting a grammatical error within the changelog entry `src/content/changelog/logs/2025-11-05-logpush-permissions-update.mdx`. Specifically, it refines the description of **Logpush permissions** for **Zero Trust datasets**, ensuring greater clarity and accuracy for users reviewing recent changes. This is a **maintenance** task that improves the quality of the project's public-facing documentation.

This commit primarily **updates the documentation** for the **Logpush** service, focusing on its permission requirements. It introduces a new changelog entry in `src/content/changelog/logs/2025-11-05-logpush-permissions-update.mdx` that details **updated permission requirements** for Logpush jobs, specifically concerning **Zero Trust datasets**. Additionally, an older changelog entry related to IBM Cloud Logs integration is removed. This **documentation update** ensures users are informed about necessary permission adjustments for configuring Logpush with Zero Trust data, serving as a critical **maintenance** and informational update.

This commit **introduces documentation** for the **Azure Sentinel Connector**, adding a new changelog entry (`src/content/changelog/logs/2025-10-27-Sentinel-connector.mdx`) that details its features and benefits. This work represents a **new capability announcement** within the **log integrations** subsystem. Concurrently, an outdated documentation file for `IBM-cloud-logs-integration.mdx` is **removed**, streamlining the available integration guides. The primary impact is to inform users about the availability of the **MS Sentinel connector** and update the project's integration offerings.

This commit provides crucial **documentation updates** for the **Audit Logs v2** system, primarily focusing on its new **Logpush** capability. It **announces the beta release of the Audit Logs v2 Logpush feature** by adding a new changelog entry in `src/content/changelog/audit-logs/2025-08-22-audit-logs-v2-logpush.mdx`. Concurrently, it refines the existing documentation for the **Audit Logs v2 UI**, updating instructions for enabling it and removing an outdated screenshot in `src/content/changelog/audit-logs/2025-07-29-audit-logs-v2-ui-beta.mdx`. This work ensures users are well-informed about the latest features and have accurate guidance for interacting with the Audit Logs v2 platform.

This commit primarily focuses on **documentation updates** within the project's changelog. It introduces a new entry to the **Logpush service** changelog, specifically documenting the new **dedicated egress IPs feature**. The update is located at `src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx`, informing users about this significant new capability. This **documentation update** ensures that users are properly notified and can understand the scope of the dedicated egress IP functionality for their Logpush configurations.

This commit introduces a **new integration** for the **Logpush service**, enabling it to send logs to **IBM Cloud Logs** as a destination. The primary change involves adding a changelog entry (`src/content/changelog/logs/2025-08-13-ibm-cloud-logs-destination.mdx`) to announce this **new capability**. This enhancement expands the available log destinations, providing users with greater flexibility for log management and analysis by supporting IBM Cloud Logs.

This commit **announces the beta release** of the **Audit Logs v2 UI** by adding a new entry to the project's changelog. It specifically updates the **documentation** within `src/content/changelog/audit-logs/` to inform users about the availability of this significant **new capability**. The changelog entry details the **features and known issues** of the updated user interface for the **Audit Logs** subsystem, encouraging user engagement with the beta program. This ensures proper communication regarding the latest iteration of the audit logging functionality.

This commit **updates the documentation** for the **logging system**, specifically within the `custom-fields` reference (`src/content/docs/logs/reference/custom-fields.mdx`). It **removes a previously stated limitation** on logging **transformed headers**, indicating that this functionality is now fully supported by the system. This **documentation update** clarifies custom field configurations, providing users with more accurate information regarding the system's capabilities and increased flexibility when configuring log data.

This commit introduces a **documentation update** by adding a new changelog entry. It details a **new capability** within the **custom fields** feature, specifically enabling support for **raw and transformed values** when applied to **request and response headers**. This enhancement provides users with greater flexibility in defining and utilizing header data, ensuring they are aware of the advanced processing options available. The update to `src/content/changelog/logs/2025-04-18-custom-fields-raw-transformed-values.mdx` informs users about this significant improvement.

This commit **removes previously enforced header limits** specifically for **custom fields**. This change enhances the flexibility and robustness of the **custom fields subsystem**, allowing for a greater number or length of headers to be associated with custom data. As a **feature enhancement**, it prevents potential data truncation or integration issues that arose from arbitrary header restrictions, improving the overall usability and data handling capabilities for custom field configurations.

This commit **documents** the **beta release** of **Automatic Audit Logs (version 2)** by adding a new changelog entry, detailing key improvements and known limitations for this significant **new capability**. Concurrently, a new product configuration file, `src/content/products/audit-logs.yaml`, is introduced to define the product's metadata, including its title, group, URL, and visibility. This **documentation** and **configuration update** ensures the **Audit Logs product** is properly announced and integrated within the system.

This commit **updates the project's changelog** by adding a new entry announcing the **one-click Logpush setup with R2 Object Storage**. This **documentation update** informs users about a significant new capability, simplifying the configuration process for Logpush to R2. The new entry, located at `src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx`, also incorporates links to relevant developer documentation for further details. This change primarily affects the **documentation** subsystem and serves as a **feature announcement** for the Logpush service.