# Jaeger

### Description

This Jaeger destination configures an OTLP exporter to send traces to a Jaeger server for ingestion. Replaces the pre-existing Jaeger destination that utilized a Jaeger specific exporter.

### Supported Types

| Metrics | Logs | Traces | Bindplane Collector |
| ------- | ---- | ------ | ------------------- |
|         |      | ✓      | `v1.36.0`+          |

### Configuration

| Field                              | Description                                                                                                                                                                       |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Hostname                           | Hostname or IP address of the Jaeger server.                                                                                                                                      |
| Port                               | Port of the Jaeger server, either gRPC or HTTP depending on `Protocol`, to send OTLP data to. [Read more](https://www.jaegertracing.io/docs/1.50/getting-started/).               |
| Protocol                           | The OTLP protocol to use when sending to the Jaeger server. Can be gRPC or HTTP.                                                                                                  |
| Compression                        | Compression algorithm to use when sending data to the OTLP server. Ensure that the server supports the compression algorithm selected. Kinds of compression depend on `Protocol`. |
| Additional Headers                 | Add additional headers to be attached to each request.                                                                                                                            |
| Enable TLS                         | Whether or not to use TLS.                                                                                                                                                        |
| Skip TLS Certificate Verification  | Enable to skip TLS certificate verification.                                                                                                                                      |
| TLS Certificate Authority File     | Certificate authority used to validate TLS certificates.                                                                                                                          |
| Mutual TLS                         | Whether or not to use mutual TLS authentication.                                                                                                                                  |
| Mutual TLS Client Certificate File | A TLS certificate used for client authentication.                                                                                                                                 |
| Mutual TLS Client Private Key File | A TLS private key used for client authentication.                                                                                                                                 |

This destination supports the [retry settings](/configuration/bindplane-otel-collector/retry-on-failure.md), the [sending queue settings](/configuration/bindplane-otel-collector/sending-queue.md), and the [persistent queue settings.](/configuration/bindplane-otel-collector/persistent-queue.md)

| Sending Queue | Persistent Queue | Retry on Failure |
| ------------- | ---------------- | ---------------- |
| ✓             | ✓                | ✓                |

### Example Configuration

#### Basic Configuration

For basic configuration, we specify the `hostname` of the Jaeger server traces are going to be sent to, as well as what `protocol` will be used (in this case gRPC).

**Web Interface**

<figure><img src="/files/Yqkj59VYRzJcj7XXvdnf" alt="Bindplane docs - Jaeger - image 1"><figcaption></figcaption></figure>

**Standalone Destination**

```yaml
apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  id: jaeger_otlp
  name: jaeger_otlp
spec:
  type: jaeger_otlp
  parameters:
    - name: hostname
      value: '0.0.0.0'
    - name: protocol
      value: 'grpc'
    - name: grpc_port
      value: '4317'
    - name: enable_tls
      value: 'false'
```

#### Advanced Configuration

This configuration is similar to the basic configuration but also utilizes TLS, Sending Queue, Persistent Queue, and Retry on Failure.

**Web Interface**

<figure><img src="/files/XYG5E2OujseZq7j8sXKU" alt="Bindplane docs - Jaeger - image 2"><figcaption></figcaption></figure>

<figure><img src="/files/Z1nSyz4Z4cFXTsQcpeuy" alt="Bindplane docs - Jaeger - image 3"><figcaption></figcaption></figure>

**Standalone Destination**

```yaml
apiVersion: bindplane.observiq.com/v1
kind: Destination
metadata:
  id: jaeger_otlp
  name: jaeger_otlp
spec:
  type: jaeger_otlp
  parameters:
    - name: hostname
      value: '0.0.0.0'
    - name: protocol
      value: 'grpc'
    - name: grpc_port
      value: '4317'
    - name: grpc_compression
      value: 'gzip'
    - name: enable_tls
      value: 'true'
    - name: ca_file
      value: '/some_ca_file'
    - name: retry_on_failure_enabled
      value: 'true'
    - name: sending_queue_enabled
      value: 'true'
    - name: persistent_queue_enabled
      value: true
    - name: persistent_queue_storage_extension
      value: 
        type: file_storage_persistent_queue
        parameters:
          - name: persistent_queue_directory
            value: ${OIQ_OTEL_COLLECTOR_HOME}/storage
          - name: timeout
            value: 1
          - name: persistent_queue_fsync
            value: true
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bindplane.com/integrations/destinations/jaeger.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.