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

Introduction

Bloomreach Cloud customers can stream application logs from their Bloomreach Experience Manager (brXM) environments directly into their existing observability platform using the OpenTelemetry (OTLP) standard. This gives your SRE and operations teams a single, centralized view of Bloomreach alongside the rest of your stack.

OpenTelemetry log streaming is an opt‑in capability configured per Bloomreach Cloud stack and delivered as a managed platform service.

When to Use OpenTelemetry Log Streaming

Use OpenTelemetry log streaming if you:

• Already operate a centralized observability platform such as Dynatrace, Splunk, Grafana Cloud, or any other OTLP‑compatible solution.

• Want one pane of glass for Bloomreach logs together with the rest of your applications and infrastructure.

• Prefer to manage log retention, alerting policies, and access control entirely within your own monitoring stack.

If you do not yet have an observability platform, or if you are satisfied with the default Humio‑based monitoring, you can continue to use Monitor Application Logs using Humio instead. Once you enable OpenTelemetry log streaming, both platforms run in parallel for 60 days so you can verify your logs in both Humio and your observability platform simultaneously. After the 60‑day grace period, Humio access for your stack will be revoked.

How It Works

At a high level:

• Bloomreach Cloud runs an OpenTelemetry Collector alongside your CMS and Site applications in the cluster.

• Application logs are exported in OTLP format from Bloomreach Cloud into your observability backend over HTTPS, using the endpoint and credentials you provide.

• Your observability platform handles ingestion, storage, dashboards, and alerting. Bloomreach Cloud is responsible only for reliably pushing logs out.

This is a log‑push integration, not a pull mechanism: Bloomreach Cloud does not host an API for log retrieval.

Supported Use Cases and Scope

The first phase of this capability focuses on logs from Bloomreach Cloud stacks:

• In scope today

  • CMS and Site application logs from supported Bloomreach Cloud stacks.

  • Delivery to any OTLP‑compatible observability backend (for example Dynatrace, Splunk, or Grafana Cloud).

• Planned / roadmap (not covered by this page)

  • OpenTelemetry traces from brXM(currently only available for self hosted customers- see OpenTelemetry Integration)

  • OpenTelemetry metrics from Bloomreach Cloud and brXM.

Check the brXM Release Notes and your account team for the latest status on metrics and tracing support.

Requirements

To use OpenTelemetry log streaming, you need:

• A stack running in Bloomreach Cloud (PaaS).

• An OTLP ingest endpoint in your observability platform (for example, a Dynatrace OTLP log ingest URL).

• An access token / API key and any required HTTP headers with permission to ingest logs.

• A technical contact on your side (SRE / observability owner) to validate ingestion.

Enabling OpenTelemetry Log Streaming

1. Request Enablement

OpenTelemetry log streaming is enabled per stack and is not turned on by default.

1. Open a ticket with Bloomreach Support.

2. Include:

   • Your stack name (for example, my-stack).

   • Your target observability platform (for example, Dynatrace, Splunk, Grafana Cloud).

   • A technical contact for observability on your side.

Support will confirm eligibility and coordinate a start date, typically beginning with a time‑boxed POC on one stack.

2. Provide OTLP Endpoint and Credentials

Your observability owner needs to provide the connection details required by the OpenTelemetry Collector:

• OTLP endpoint URL for log ingestion (for example, Dynatrace OTLP log ingest endpoint).

• Authentication

  • Access token or API key with log‑ingest permissions.

  • Any required HTTP headers (for example, Authorization, tenant IDs, or region headers).

These values are supplied to Bloomreach via your support ticket, and the Bloomreach Cloud team configures 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 the selected stack.

2. Logs from your CMS and Site applications are routed to the collector and forwarded to your observability platform.

Bloomreach will confirm when streaming has been enabled for your environments.

4. Verify Logs in Your Observability Platform

Once streaming is enabled:

1. Open your observability platform and navigate to the logs section for the configured OTLP endpoint.

2. Filter by:

   • Service / application corresponding to your Bloomreach CMS / Site.

   • Environment / stack attributes (for example, production vs. acceptance).

3. Trigger a simple CMS or site action (for example, loading the CMS login page) and confirm that:

   • New log entries appear.

   • Timestamps and severity levels look correct.

   • Stack and environment metadata are present.

Work with your observability team to create the dashboards and alerts you need.

Log Fields and Metadata

While the exact attribute names depend on your observability backend, each log entry includes metadata that helps you filter and correlate issues:

• Stack name – identifies the Bloomreach Cloud stack (for example, mycloud.bloomreach.io).

• Environment – environment name within the stack (for example, blue, green, acc, prod).

• Application / container – whether the log originated from CMS, Site, or other services (for example, cms-log, site-log).

• Severity / log level – for example, INFO, WARN, ERROR.

Use these attributes to:

• Build per‑stack or per‑environment dashboards.

• Set targeted alerts (for example, ERROR logs in production only).

• Correlate Bloomreach logs with upstream or downstream systems in the same observability platform.

Coexistence with Existing Logging

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

• Humio‑based logging (the default for Bloomreach Cloud).

• OpenTelemetry log streaming to your own observability backend.

Use this period to verify your logs in your observability platform. After 60 days, Humio access for your stack will be revoked. If you need an extension, contact Bloomreach Support before the grace period ends.

Operational Responsibilities

• Bloomreach Cloud

  • Operates the OpenTelemetry Collector and the outbound log pipeline for your stack.

  • Ensures logs are exported from Bloomreach Cloud in OTLP format to the configured endpoint.

• You (Customer)

  • Own and operate the observability platform (for example, Dynatrace, Splunk, Grafana Cloud).

  • Manage dashboards, alert rules, retention and access control for Bloomreach logs alongside your other systems.