Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

Integration with jaeger operator #940

Open
serg-bs opened this issue Dec 2, 2021 · 1 comment
Open

Integration with jaeger operator #940

serg-bs opened this issue Dec 2, 2021 · 1 comment

Comments

@serg-bs
Copy link

serg-bs commented Dec 2, 2021

Is your feature request related to a problem? Please describe.
I install jaeger operator, backend

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
    name: simple-prod
spec:
    strategy: production
    ingress:
        enabled: false
    agent:
      strategy: DaemonSet
    storage:
        type: elasticsearch
        options:
            es:
                server-urls: http://opendistro-elastic:9200
                username:  username
                password: password

Supported storage backend could not be data prepper
May be some Storage plugin should we use in this case?

How to set up data-prepper in such cases ?

@sshivanii
Copy link
Contributor

Hi @serg-bs

Considering you have an existing Jaeger based application, I'd recommend following this Jaeger HotROD example to use Data Prepper's trace analytics feature.

The supported storage backend in Data Prepper is an OpenSearch sink. You can use an Otel collector, transform the collected telemetry data using Data Prepper and write it to OpenSearch. You can follow this Getting Started guide to setup Data Prepper, and for trace observability, follow this Trace Analytics guide.

P.S. This Data Prepper repository is inactive and we've moved to OpenSearch Data Prepper for issues and active development. To help you migrate, we have a simple Migration Guide.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants