Skip to content

No traces appear in Jaeger after deploying SocialNetwork via Helm and running wrk2 load test #366

@xh616

Description

@xh616

Environment:

Project: DeathStarBench/socialNetwork

Deployment method: Helm chart

Kubernetes cluster: k8s 1.30

Jaeger: deployed by Helm chart along with the app

Problem

After deploying the SocialNetwork application using Helm and exposing Jaeger via NodePort, I run wrk2 to generate load.

Image

However, no service traces appear in the Jaeger UI — only Jaeger’s own internal services show up.

I expected that the microservices in SocialNetwork (user, media, post, social-graph, etc.) would generate spans and appear in Jaeger’s service dropdown, but the list is empty.

Image

Is there anything missing in the Helm deployment, or do I need to manually enable tracing for the SocialNetwork services?

Has anyone encountered the same issue when deploying via Helm + Kubernetes + Jaeger?

Any guidance or configuration hints would be greatly appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions