Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that tracing (jaeger, oltp) is working #1105

Open
5 tasks done
ctron opened this issue Dec 17, 2024 · 3 comments
Open
5 tasks done

Ensure that tracing (jaeger, oltp) is working #1105

ctron opened this issue Dec 17, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@ctron
Copy link
Contributor

ctron commented Dec 17, 2024

Right now it seems that the tracing integration is broken.

βœ… Expectations

  • we can deploy jaeger on minikube (all in one configuration)
  • we can tell trustify v2 to send tracing information to this instance

πŸ”₯ Problem

  1. I see the following errors in the pod logs:

    OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: tcp connect error: Connection refused (os error 111)
    
  2. I don't see tracing information in the jaeger instance.

♻️ Reproduce

  • Clone helm chart repository

    git clone git@github.com:trustification/trustify-helm-charts.git
    cd trustify-helm-charts
  • Run minikube

    minikube start --cpus 4 --memory 12288 --disk-size 20gb --addons ingress,dashboard
  • Set env

    NAMESPACE=trustify
    APP_DOMAIN=.$(minikube ip).nip.io
    kubectl create ns $NAMESPACE
    kubectl config set-context --current --namespace=$NAMESPACE
  • Deploy infrastructure chart with jaeger enabled

    helm upgrade --install --dependency-update -n $NAMESPACE infrastructure charts/trustify-infrastructure --values values-minikube.yaml --set-string keycloak.ingress.hostname=sso$APP_DOMAIN --set-string appDomain=$APP_DOMAIN --set jaeger.enabled=true --set-string jaeger.allInOne.ingress.hosts[0]=jaeger$APP_DOMAIN --set tracing.enabled=true
  • Deploy application with tracing enabled

    helm upgrade --install -n $NAMESPACE trustify charts/trustify --values values-minikube.yaml --set-string appDomain=$APP_DOMAIN --set tracing.enabled=true

⬇️ Steps

  • Try to reproduce the issue
  • Solve the connection issue (this may include changes in the helm chart repo or trustify itself)
  • Verify that the traces show up in jaeger
@ctron ctron added the bug Something isn't working label Dec 17, 2024
@ctron ctron added this to Trustify Dec 17, 2024
@ctron ctron moved this to In progress in Trustify Dec 17, 2024
@helio-frota
Copy link
Collaborator

progress πŸ‘ I was able to see some traces on jaeger (locally) using a bit-hacked pm-mode version

2024-12-18_08-41

@helio-frota
Copy link
Collaborator

progress πŸ‘ able to see traces with

cargo run --bin trustd api --db-password trustify --devmode --auth-disabled --tracing enabled

2024-12-18_15-09

Although:

  • This is not related to the original error in this issue
  • Need to increase trace ratio to something > 1
  • Need to comment EnvFilter as I have no idea how to make it work:

2024-12-18_15-01

@helio-frota
Copy link
Collaborator

progress πŸ‘
the issue changed now to received message with invalid compression flag: 60 (valid flags are 0 and 1)
trustification/trustify-helm-charts#11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: In progress
Development

No branches or pull requests

2 participants