No trace information on AKS #1025
Closed
bardagadvergur
announced in
Community Discussions
Replies: 1 comment 1 reply
-
|
@bardagadvergur it looks like GitHub gave you a duplicate here of #1024 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi ... I am completely lost as to what my issue can be so reaching out for help. I've added OpenTelemetry tracing to my .net core 6.0 application and in my local dev environment running in docker everything works as expected and traces are being exported. This is my tracing config:
`
public static IServiceCollection AddTracing(this IServiceCollection services, string appName, IConfiguration configuration)
{
`
So locally I can see my traces in Jaeger as well as in the console. But when I deploy this application to my AKS kubernetes cluster no traces seem to be exported. I've validated the connection between tempo & my service using netcat & tcpdump so connectivity should not be an issue. I've also exposed the jaeger port of tempo in my cluster and have sent traces from my local environment into tempo running in the cluster so tempo is accepting traces just fine. After I was certain network connectivity was not an issue I added the console exporter and to my surprise no traces are visible in the logs on AKS.
These are the OpenTelemetry packages I am using:
`
`
Beta Was this translation helpful? Give feedback.
All reactions