OpenTelemetry Log Streaming: Monitor Application Logs Using Your Existing Observability Platform

Overview

Bloomreach Cloud allows you to stream application logs from your Bloomreach Content environments directly to your existing observability platform using the OpenTelemetry (OTLP) standard. This integration enables your SRE and operations teams to monitor Bloomreach logs alongside the rest of your infrastructure in a centralized location.

OpenTelemetry log streaming is an opt-in feature. You configure it per Bloomreach Cloud stack, and Bloomreach manages the service.

When to Use OpenTelemetry Log Streaming

Enable OpenTelemetry log streaming if you:

• Use a centralized observability platform such as Dynatrace, Splunk, Grafana Cloud, or any other OTLP-compatible solution.
• Require a unified view of Bloomreach logs with your other applications and infrastructure.
• Prefer to manage log retention, alerting, and access control within your own monitoring tools.

If you do not use an observability platform, or if the default Humio-based monitoring meets your needs, continue using Monitor Application Logs using Humio. After you enable OpenTelemetry log streaming, both Humio and your observability platform will receive logs for 60 days. Use this period to verify log ingestion. After 60 days, Humio access for your stack is revoked.

How OpenTelemetry Log Streaming Works

• Bloomreach Cloud deploys an OpenTelemetry Collector alongside your CMS and Site applications in the cluster.
• The collector exports application logs in OTLP format over HTTPS to your observability backend, using the endpoint and credentials you provide.
• Your observability platform handles log ingestion, storage, dashboards, and alerting. Bloomreach Cloud is responsible for exporting logs.

This integration is push-based. Bloomreach Cloud does not provide an API for log retrieval.

Supported Use Cases and Scope

Current support includes:

• CMS and Site application logs from supported Bloomreach Cloud stacks.
• Delivery to any OTLP-compatible observability backend (for example, Dynatrace, Splunk, Grafana Cloud).

Planned but not currently available:

• OpenTelemetry traces from Bloomreach Content (currently available only for self-hosted customers; see OpenTelemetry Integration).
• OpenTelemetry metrics from Bloomreach Cloud and Bloomreach Content.

Refer to the Bloomreach Content Release Notes or contact your account team for updates on metrics and tracing support.

Requirements

To use OpenTelemetry log streaming, you need:

• A stack running on Bloomreach Cloud (PaaS).
• An OTLP ingest endpoint in your observability platform (for example, a Dynatrace OTLP log ingest URL).
• An access token or API key, and any required HTTP headers, with permission to ingest logs.
• A technical contact (such as an SRE or observability owner) to validate log ingestion.

Enabling OpenTelemetry Log Streaming

1. Request Enablement

OpenTelemetry log streaming is disabled by default and must be enabled per stack.

1. Open a ticket with Bloomreach Support.
2. Provide the following information:
   • Your stack name (for example, my-stack).
   • The target observability platform (for example, Dynatrace, Splunk, Grafana Cloud).
   • A technical contact for observability on your team.

Bloomreach Support will confirm eligibility and coordinate a start date, typically starting with a time-boxed proof of concept on one stack.

2. Provide OTLP Endpoint and Credentials

Your observability owner must supply the following connection details for the OpenTelemetry Collector:

• The OTLP endpoint URL for log ingestion (for example, a Dynatrace OTLP log ingest endpoint).
• Authentication details:
  • Access token or API key with log-ingest permissions.
  • Any required HTTP headers (such as Authorization, tenant IDs, or region headers).

Submit these details through your support ticket. The Bloomreach Cloud team will configure the collector on your stack.

3. Bloomreach Cloud Configuration and Rollout

After you provide the endpoint and credentials:

1. Bloomreach Cloud configures the OpenTelemetry Collector for your stack.
2. Logs from your CMS and Site applications are routed to the collector and forwarded to your observability platform.

Bloomreach will notify you when streaming is enabled for your environments.

4. Verify Logs in Your Observability Platform

After streaming is enabled:

1. Access your observability platform and navigate to the logs section for the configured OTLP endpoint.
2. Filter logs by:
   • Service or application (Bloomreach CMS or Site).
   • Environment or stack attributes (such as production or acceptance).
3. Perform a basic CMS or Site action (such as loading the CMS login page) and verify:
   • New log entries appear.
   • Timestamps and severity levels are correct.
   • Stack and environment metadata are present.

Work with your observability team to create dashboards and alerts as needed.

Log Fields and Metadata

Each log entry includes metadata to support filtering and correlation. Attribute names may vary by observability backend, but typically include:

• Stack name: Identifies the Bloomreach Cloud stack (for example, mycloud.bloomreach.io).
• Environment: The environment name within the stack (such as blue, green, acc, prod).
• Application or container: Indicates the log source (such as cms-log or site-log).
• Severity or log level: For example, INFO, WARN, ERROR.

Use these attributes to:

• Build dashboards by stack or environment.
• Set targeted alerts (for example, ERROR logs in production).
• Correlate Bloomreach logs with other systems in your observability platform.

Coexistence with Existing Logging

When you enable OpenTelemetry log streaming, Bloomreach Cloud runs both log pipelines in parallel for a 60-day grace period:

• Humio-based logging (default for Bloomreach Cloud)
• OpenTelemetry log streaming to your observability backend

Use this period to verify logs in your observability platform. After 60 days, Humio access for your stack is revoked. To request an extension, contact Bloomreach Support before the grace period ends.

Operational Responsibilities

• Bloomreach Cloud:
  • Operates the OpenTelemetry Collector and outbound log pipeline for your stack.
  • Exports logs from Bloomreach Cloud in OTLP format to your configured endpoint.
• Customer:
  • Owns and operates the observability platform (such as Dynatrace, Splunk, or Grafana Cloud).
  • Manages dashboards, alert rules, retention, and access control for Bloomreach logs alongside other systems.