byoc-logs: remove Preview

content/en/byoc-logs/_index.md

@@ -9,10 +9,6 @@ aliases:
   - /cloudprem/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 BYOC Logs is Datadog's log management solution for organizations that want to keep their data in their own cloud accounts and control costs using their existing cloud provider discounts. It is built to meet stringent security, data residency, regulatory, and high-volume requirements.
 
 

content/en/byoc-logs/configure/_index.md

@@ -12,15 +12,11 @@ aliases:
   - /cloudprem/configure/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 After installing BYOC Logs, you can configure your deployment to meet your environment, security, and performance requirements. Key configuration areas include account integration, cloud resource setup, cluster sizing, ingress, and processing options. These settings allow you to tailor BYOC Logs for your specific needs.
 
-If you don't see the BYOC Logs entry in the Logs menu, it means BYOC Logs is not activated on your account. Join the [BYOC Logs Preview][1] to activate BYOC Logs on your account.
+If you don't see the BYOC Logs entry in the Logs menu, it means BYOC Logs is not activated on your account. Contact your Datadog account team to activate BYOC Logs on your account.
 
 {{< whatsnext desc="Customize your BYOC Logs deployment:">}}
    {{< nextlink href="/byoc-logs/configure/indexes/" >}}Configure indexes{{< /nextlink >}}

content/en/byoc-logs/configure/indexes.md

@@ -13,10 +13,6 @@ further_reading:
   text: "Search Logs"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 By default, a BYOC Logs cluster stores all logs in a single index with a single retention policy. With multiple indexes, you can segment logs by defining filter queries and assigning a different retention period to each index. For example, you can retain audit logs for 1 year while keeping debug logs for only 3 days.
 
 To view and manage your BYOC Logs indexes, navigate to the [BYOC Logs page][1] in Datadog. Select a cluster and click {{< ui >}}View Indexes{{< /ui >}} to access the index configuration.

content/en/byoc-logs/configure/ingress.md

@@ -12,10 +12,6 @@ aliases:
   - /cloudprem/configure/ingress/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 Ingress is a critical component of your BYOC Logs deployment. The Helm chart automatically creates two ingress configurations called public ingress and internal ingress. If the AWS Load Balancer Controller is installed on the cluster, it provisions one ALB per ingress configuration. Each load balancer can be further configured using ingress annotations.

content/en/byoc-logs/configure/lambda.md

@@ -12,10 +12,6 @@ aliases:
   - /cloudprem/configure/lambda/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 <div class="alert alert-warning">Lambda search offloading is an experimental feature.</div>
 
 <div class="alert alert-info">Lambda search offloading is only available on AWS.</div>

content/en/byoc-logs/configure/pipelines.md

@@ -13,10 +13,6 @@ further_reading:
   text: "Troubleshooting"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 BYOC Logs includes a processing feature that allows you to parse and enrich logs. It automatically parses logs formatted in JSON. You can define pipelines and processors to extract meaningful information or attributes from semi-structured text, which can then be used for aggregations.

content/en/byoc-logs/guides/_index.md

@@ -17,10 +17,6 @@ aliases:
 ---
 
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 {{< whatsnext desc="Explore the following guides:">}}
    {{< nextlink href="/byoc-logs/guides/query_logs_with_mcp/" >}}Query BYOC Logs with the Datadog MCP Server{{< /nextlink >}}
    {{< nextlink href="/byoc-logs/guides/send_otel_logs_observability_pipelines/" >}}Send OpenTelemetry Logs to BYOC Logs through Observability Pipelines{{< /nextlink >}}

content/en/byoc-logs/guides/query_logs_with_mcp.md

@@ -15,10 +15,6 @@ aliases:
   - /cloudprem/guides/query_logs_with_mcp/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 The [Datadog MCP (Model Context Protocol) server][1] allows you to query your Datadog logs, including logs stored in BYOC Logs indexes, directly through AI-powered tools and integrations. Querying BYOC Logs with the Datadog MCP server unlocks several valuable capabilities, including:

content/en/byoc-logs/guides/send_otel_logs_observability_pipelines.md

@@ -15,10 +15,6 @@ aliases:
   - /cloudprem/guides/send_otel_logs_observability_pipelines/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 BYOC Logs supports log ingestion from OTEL collectors by using Observability Pipelines as the ingestion layer. This guide provides step-by-step instructions to connect OTEL logs to BYOC Logs—without disrupting your existing OTEL configuration.
@@ -32,7 +28,7 @@ By the end of this guide, you will be able to:
 
 ## Prerequisites
 
-- [BYOC Logs Preview][1] access.
+- BYOC Logs access. Contact your Datadog account team to request access.
 - **Datadog API Key**: [Get your API key][2].
 - **Datadog Application Key**: [Get your application key][3].
 - **Docker**: [Install Docker][4].

content/en/byoc-logs/ingest/_index.md

@@ -5,10 +5,6 @@ aliases:
   - /cloudprem/ingest/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 After installing and configuring BYOC Logs, you need to set up log ingestion to start sending log data from your applications and infrastructure. BYOC Logs supports multiple ingestion methods to accommodate different architectures and requirements.

content/en/byoc-logs/ingest/agent.md

@@ -16,10 +16,6 @@ further_reading:
   text: "Datadog Operator Guide"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 This document provides configuration steps for using the Datadog Agent to send logs to a Datadog BYOC Logs deployment. Unlike the Datadog SaaS platform, BYOC Logs requires specific Agent configurations to ensure logs are enriched with necessary host-level tags and sent to the correct endpoint. This guide covers how to set these configurations for the most common deployment methods.
 

content/en/byoc-logs/ingest/api.md

@@ -13,10 +13,6 @@ further_reading:
   text: "Observability Pipelines Integration"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 You can send logs to BYOC Logs using direct REST API calls. This method is useful for custom integrations or scripts that can't use a Datadog Agent or Observability Pipelines.

content/en/byoc-logs/ingest/observability_pipelines.md

@@ -19,10 +19,6 @@ further_reading:
   text: "Datadog BYOC Logs destination for Observability Pipelines"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 Observability Pipelines provides a flexible intermediary layer between your Datadog Agents and BYOC Logs, allowing you to process, transform, and route logs before they reach your BYOC Logs deployment. Configure Observability Pipelines to receive logs from the Datadog Agent and forward them to BYOC Logs:

content/en/byoc-logs/install/_index.md

@@ -5,10 +5,6 @@ aliases:
   - /cloudprem/install/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 BYOC Logs requires **Kubernetes** for production deployments. It is supported on cloud-managed Kubernetes services (EKS, GKE, AKS) and self-managed Kubernetes clusters. A [Docker installation][2] is also available for local evaluation and testing only.

content/en/byoc-logs/install/aws_eks.md

@@ -13,10 +13,6 @@ further_reading:
   text: "Configure Log Ingestion"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 This document walks you through the process of configuring your AWS environment and installing BYOC Logs on AWS EKS.

content/en/byoc-logs/install/azure_aks.md

@@ -6,10 +6,6 @@ aliases:
 description: Learn how to install and configure BYOC Logs on Azure AKS
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 This document walks you through the process of configuring your Azure environment and installing BYOC Logs on Azure AKS.

content/en/byoc-logs/install/custom_k8s.md

@@ -15,10 +15,6 @@ aliases:
   - /cloudprem/install/custom_k8s/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 This documentation walks you through the process of installing BYOC Logs on any Kubernetes cluster using PostgreSQL for metadata storage and MinIO for S3-compatible object storage.

content/en/byoc-logs/install/docker.md

@@ -13,10 +13,6 @@ aliases:
 ---
 
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 <div class="alert alert-warning">

content/en/byoc-logs/install/gcp_gke.md

@@ -11,10 +11,6 @@ aliases:
   - /cloudprem/install/gcp_gke/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 This installation setup walks you through deploying Datadog BYOC Logs on Google Kubernetes Engine (GKE).

content/en/byoc-logs/introduction/_index.md

@@ -5,10 +5,6 @@ aliases:
   - /cloudprem/introduction/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 BYOC Logs is Datadog's log management solution that runs in your own infrastructure. It indexes and stores logs in your object storage, executes search and analytics queries, and connects to the Datadog UI for a fully integrated experience. BYOC Logs is designed for organizations with specific requirements:

content/en/byoc-logs/introduction/architecture.md

@@ -9,10 +9,6 @@ further_reading:
   text: "BYOC Logs Installation Prerequisites"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 {{< img src="/cloudprem/overview_architecture.png" alt="BYOC Logs architecture showing Indexers, Searchers, Metastore, and Control Plane components interacting with object storage" style="width:100%;" >}}

content/en/byoc-logs/introduction/features.md

@@ -5,9 +5,6 @@ aliases:
   - /cloudprem/introduction/features/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
 ## Overview
 
 Datadog BYOC Logs brings core Log Explorer capabilities to your self-hosted environment. This page outlines available features, notes any differences from the SaaS platform, and helps you plan your log workflows.

content/en/byoc-logs/introduction/network.md

@@ -8,10 +8,6 @@ aliases:
   - /cloudprem/introduction/network/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 This document provides an overview of how BYOC Logs and Datadog communicate with each other.
 
 ## Reverse connection (default)

content/en/byoc-logs/operate/_index.md

@@ -5,10 +5,6 @@ aliases:
   - /cloudprem/operate/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 Manage your BYOC Logs deployment with guides on sizing, monitoring, and troubleshooting.

content/en/byoc-logs/operate/best_practices.md

@@ -13,10 +13,6 @@ further_reading:
   text: "Troubleshooting"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 This page outlines operational best practices for running BYOC Logs in production to help reduce common deployment issues.

content/en/byoc-logs/operate/monitoring.md

@@ -5,10 +5,6 @@ aliases:
   - /cloudprem/operate/monitoring/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Dashboards
 
 BYOC Logs provides an out-of-the-box dashboard that monitors BYOC Logs' key metrics.

content/en/byoc-logs/operate/search_logs.md

@@ -15,10 +15,6 @@ aliases:
   - /cloudprem/operate/search_logs/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Explore BYOC Logs in the Logs Explorer
 
 1. Go to the [Datadog Log Explorer][1].

content/en/byoc-logs/operate/sizing.md

@@ -18,10 +18,6 @@ further_reading:
 
 {{< jqmath-vanilla >}}
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 Proper cluster sizing helps ensure optimal performance, cost efficiency, and reliability for your BYOC Logs deployment. Your sizing requirements depend on several factors including log ingestion volume, query patterns, retention period, and the complexity of your log data.

content/en/byoc-logs/operate/troubleshooting.md

@@ -12,10 +12,6 @@ further_reading:
   text: "Observability Pipelines Scaling and Performance"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 This page provides troubleshooting guidance for common issues you may encounter when deploying or operating Datadog BYOC Logs. It includes typical error messages, diagnostic steps, and tips for resolving problems related to access permissions, storage configuration, and component health. Use this guide to quickly diagnose issues or to gather context before reaching out to [Datadog support][1].

content/en/byoc-logs/quickstart.md

@@ -12,10 +12,6 @@ aliases:
   - /cloudprem/quickstart/
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 Get started with BYOC Logs locally in less than 5 minutes. This quickstart covers the following:
@@ -26,7 +22,7 @@ Get started with BYOC Logs locally in less than 5 minutes. This quickstart cover
 
 ## Prerequisites
 
-- Ask for the [BYOC Logs Preview][1].
+- Access to BYOC Logs. Contact your Datadog account team to request access.
 - **Datadog API Key**: [Get your API key][2].
 - **Docker**: [Install Docker][3].
 

content/en/byoc-logs/release_notes.md

@@ -11,10 +11,6 @@ further_reading:
   text: "Troubleshoot BYOC Logs"
 ---
 
-{{< callout btn_hidden="true" header="Join the Preview!" >}}
-  BYOC Logs is in Preview.
-{{< /callout >}}
-
 ## Overview
 
 This page tracks releases of the **BYOC Logs binary**, distributed as a Docker image and bundled by the `datadog/cloudprem` Helm chart. New features and fixes ship in the binary; the chart packages them for deployment.