OBSERVABILITY PLATFORM
Route logs through Telemetry Pipeline

Route logs through Telemetry Pipeline

This feature is available only to specific Chronosphere Observability Platform users, and has not been announced or officially released. Do not share or discuss this feature, or information about it, with anyone outside of your organization.

You can use Chronosphere Telemetry Pipeline to ingest logs from various sources, apply parsers and processing rules, and send the output to Chronosphere Observability Platform. You create and define a pipeline in Telemetry Pipeline and set Observability Platform as a destination.

After deploying your pipeline, processed log data streams to Observability Platform and is available for exploring and querying in Logs Explorer.

Prerequisites

Before creating a pipeline, you must install Telemetry Pipeline, which includes installing a Core Operator and Core Instance.

Create a pipeline

Specify a source and destination, and apply parsers and processing rules.

To route logs through Telemetry Pipeline to Observability Platform:

  1. Create a pipeline. Follow the steps outlined in the Telemetry Pipeline documentation.

  2. Add a source, such as Fluent Bit, Elasticsearch, or OpenTelemetry.

  3. Add the Chronosphere Logs destination.

  4. Click the Chronosphere Logs destination to edit its configuration:

    1. In the General section, in the Host field, enter:

      TENANT.chronosphere.io

      Replace TENANT with the name of your Observability Platform tenant.

    2. Expand the Advanced section, and in the URI field, enter:

      /unstable/data/logs/structured
  5. Complete the remaining steps to deploy your pipeline.

After deploying your pipeline, verify that Observability Platform is receiving your logs as anticipated.