> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Route logs through Telemetry Pipeline

export const MyTenant = () => <>
    Replace <em><code>TENANT</code></em> with the name of your Observability Platform tenant.
  </>;

You can use Chronosphere Telemetry Pipeline to ingest logs from various sources such
as Fluent Bit, Open Telemetry, and HTTP, 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](/investigate/querying/query-logs) in Logs
Explorer.

## Prerequisites

Before creating a pipeline, you must [install Telemetry Pipeline](/ingest/pipeline/v2/install),
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](/ingest/pipeline/v2/build/create-modify#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](/ingest/pipeline/plugins/destination-plugins/chronosphere)
   destination.

4. Click the **Chronosphere Logs** destination to edit its configuration:
   1. In the **General** section, in the **Host** field, enter:

      ```text /TENANT/ theme={null}
      TENANT.chronosphere.io
      ```

      <MyTenant />

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

      ```text theme={null}
      /api/v1/data/logs/ingest
      ```

5. Complete the remaining steps to deploy your pipeline.

After deploying your pipeline,
[verify that Observability Platform is receiving your logs](/ingest/logs/verify-logs)
as anticipated.