Facing the issue after runnig the Jaeger UI #348

rpancham · 2022-08-02T11:35:51Z

rpancham
Aug 2, 2022
Collaborator

I am unable to find the Traces after running the jaeger ui for fruit service.

helio-frota · 2022-08-02T11:40:28Z

helio-frota
Aug 2, 2022
Maintainer

thanks for the feedback, I'll take a look 👍

0 replies

helio-frota · 2022-08-02T12:41:11Z

helio-frota
Aug 2, 2022
Maintainer

I have all the things installed and running from a previous setup.

I'll delete and install all again to see if works

0 replies

helio-frota · 2022-08-02T13:05:53Z

helio-frota
Aug 2, 2022
Maintainer

@rpancham it continues working here

Steps you can take a look:

Did you uncomment the require('./tracer'); in app.js and redeploy the application with npm run openshift?
Did you added the the admin rights to the developer role? oc policy add-role-to-user admin developer -n opentel ?
You need to create the jaeger instance (oc apply -f tracing/jaeger.yml) before the otel collector

0 replies

rpancham · 2022-08-03T05:48:23Z

rpancham
Aug 3, 2022
Collaborator Author

Thanks @helio Frota ***@***.***> I have tried the same steps but it is not working for me . Will try it again with some other ways.

…

On Tue, Aug 2, 2022 at 6:36 PM Helio Frota ***@***.***> wrote: @rpancham <https://github.com/rpancham> it continues working here [image: 2022-08-02_10-01] <https://user-images.githubusercontent.com/6443576/182380987-66a37be0-a5a6-41a7-a5d8-dcc68004d423.png> Steps you can take a look: - Did you uncomment the require('./tracer'); in app.js and redeploy the application with npm run openshift? - Did you added the the admin rights to the developer role? oc policy add-role-to-user admin developer -n opentel ? - You need to create the jaeger instance (oc apply -f tracing/jaeger.yml) before the otel collector — Reply to this email directly, view it on GitHub <#348 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW2BEK3IOJ7R64QCGPIR72LVXEMLZANCNFSM55K2CFJA> . You are receiving this because you were mentioned.Message ID: <nodeshift-starters/nodejs-rest-http-crud/repo-discussions/348/comments/3307893 @github.com>

0 replies

helio-frota · 2022-08-03T11:47:21Z

helio-frota
Aug 3, 2022
Maintainer

I'm using the following operators versions

Can you please share the versions you are using?

thanks

0 replies

helio-frota · 2022-08-03T11:56:18Z

helio-frota
Aug 3, 2022
Maintainer

Another thing to try is to delete the opentelemetry collector instance and run the

oc apply -f tracing/opentel-collector.yml again

0 replies

rpancham · 2022-08-03T11:56:52Z

rpancham
Aug 3, 2022
Collaborator Author

Yes i am also using the same versions

…

On Wed, Aug 3, 2022 at 5:17 PM Helio Frota ***@***.***> wrote: I'm using the following operators versions [image: 2022-08-03_08-46] <https://user-images.githubusercontent.com/6443576/182600300-8ce59702-c8c1-48ed-8cdc-8848de4e38ef.png> Can you please share the versions you are using? thanks — Reply to this email directly, view it on GitHub <#348 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW2BEK5E6ZUVDV24HYOUFQTVXJL5HANCNFSM55K2CFJA> . You are receiving this because you were mentioned.Message ID: <nodeshift-starters/nodejs-rest-http-crud/repo-discussions/348/comments/3315662 @github.com>

0 replies

rpancham · 2022-08-03T12:27:33Z

rpancham
Aug 3, 2022
Collaborator Author

I tried the above command and it is throwing the error as oc apply -f tracing/opentel-collector.yml unable to recognize "tracing/opentel-collector.yml": Unauthorized unable to recognize "tracing/opentel-collector.yml": Unauthorized ✘-1 ~/Documents/node/nodejs-rest-http-crud [main ↑·6|✚ 1]

…

On Wed, Aug 3, 2022 at 5:26 PM Helio Frota ***@***.***> wrote: Another thing to try is to delete the opentelemetry collector instance and run the oc apply -f tracing/opentel-collector.yml again — Reply to this email directly, view it on GitHub <#348 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW2BEK273FLLHU2Z673XUIDVXJM63ANCNFSM55K2CFJA> . You are receiving this because you were mentioned.Message ID: <nodeshift-starters/nodejs-rest-http-crud/repo-discussions/348/comments/3315726 @github.com>

0 replies

helio-frota · 2022-08-03T15:00:38Z

helio-frota
Aug 3, 2022
Maintainer

can you please to delete the app, the database, the jaeger and opentelemetry collector instance and install all again to see what happen?

1 reply

rpancham Aug 4, 2022
Collaborator Author

Yes I did But nothing worked

helio-frota · 2022-08-04T12:08:23Z

helio-frota
Aug 4, 2022
Maintainer

Could you please run the following command:

❯ oc get pods
NAME                                 READY   STATUS      RESTARTS   AGE
my-database-949975856-4trbw          1/1     Running     3          47h
nodejs-rest-http-crud-1-deploy       1/1     Running     0          15s
nodejs-rest-http-crud-1-lq69p        0/1     Running     0          12s
nodejs-rest-http-crud-s2i-1-build    0/1     Completed   0          113s
opentel-collector-6774895d5d-grdc4   1/1     Running     0          2m7s
opentel-jaeger-5b687db5-h4jtm        2/2     Running     2          24h

And then run the oc logs for your collector and paste the results here.

in my case: oc logs opentel-collector-6774895d5d-grdc4

❯ oc logs opentel-collector-6774895d5d-grdc4
2022-08-04T12:02:51.690Z	info	builder/exporters_builder.go:255	Exporter was built.	{"kind": "exporter", "name": "logging"}
2022-08-04T12:02:51.690Z	info	builder/exporters_builder.go:255	Exporter was built.	{"kind": "exporter", "name": "jaeger"}
2022-08-04T12:02:51.690Z	info	builder/pipelines_builder.go:224	Pipeline was built.	{"kind": "pipeline", "name": "traces"}
2022-08-04T12:02:51.690Z	info	builder/receivers_builder.go:226	Receiver was built.	{"kind": "receiver", "name": "otlp", "datatype": "traces"}
2022-08-04T12:02:51.690Z	info	service/telemetry.go:108	Setting up own telemetry...
2022-08-04T12:02:51.692Z	info	service/telemetry.go:128	Serving Prometheus metrics	{"address": ":8888", "level": "basic", "service.instance.id": "c7034d1a-4ede-4975-ab4a-fec104c19b09", "service.version": "v0.42.0-9-g0435914"}
2022-08-04T12:02:51.692Z	info	service/service.go:82	Starting extensions...
2022-08-04T12:02:51.692Z	info	service/service.go:87	Starting exporters...
2022-08-04T12:02:51.692Z	info	builder/exporters_builder.go:40	Exporter is starting...	{"kind": "exporter", "name": "logging"}
2022-08-04T12:02:51.692Z	info	builder/exporters_builder.go:48	Exporter started.	{"kind": "exporter", "name": "logging"}
2022-08-04T12:02:51.692Z	info	builder/exporters_builder.go:40	Exporter is starting...	{"kind": "exporter", "name": "jaeger"}
2022-08-04T12:02:51.692Z	info	jaegerexporter@v0.49.0/exporter.go:186	State of the connection with the Jaeger Collector backend	{"kind": "exporter", "name": "jaeger", "state": "IDLE"}
2022-08-04T12:02:51.692Z	info	builder/exporters_builder.go:48	Exporter started.	{"kind": "exporter", "name": "jaeger"}
2022-08-04T12:02:51.692Z	info	service/service.go:92	Starting processors...
2022-08-04T12:02:51.692Z	info	builder/pipelines_builder.go:54	Pipeline is starting...	{"kind": "pipeline", "name": "traces"}
2022-08-04T12:02:51.692Z	info	builder/pipelines_builder.go:65	Pipeline is started.	{"kind": "pipeline", "name": "traces"}
2022-08-04T12:02:51.692Z	info	service/service.go:97	Starting receivers...
2022-08-04T12:02:51.692Z	info	builder/receivers_builder.go:68	Receiver is starting...	{"kind": "receiver", "name": "otlp"}
2022-08-04T12:02:51.692Z	info	otlpreceiver/otlp.go:70	Starting GRPC server on endpoint 0.0.0.0:4317	{"kind": "receiver", "name": "otlp"}
2022-08-04T12:02:51.692Z	info	otlpreceiver/otlp.go:88	Starting HTTP server on endpoint opentel-collector-headless.opentel.svc:4318	{"kind": "receiver", "name": "otlp"}
2022-08-04T12:02:52.692Z	info	jaegerexporter@v0.49.0/exporter.go:186	State of the connection with the Jaeger Collector backend	{"kind": "exporter", "name": "jaeger", "state": "CONNECTING"}
2022-08-04T12:02:56.694Z	info	builder/receivers_builder.go:73	Receiver started.	{"kind": "receiver", "name": "otlp"}
2022-08-04T12:02:56.694Z	info	service/collector.go:249	Starting otelcol...	{"Version": "0.49.0", "NumCPU": 8}
2022-08-04T12:02:56.694Z	info	service/collector.go:145	Everything is ready. Begin running and processing data.
2022-08-04T12:02:57.692Z	info	jaegerexporter@v0.49.0/exporter.go:186	State of the connection with the Jaeger Collector backend	{"kind": "exporter", "name": "jaeger", "state": "READY"}
2022-08-04T12:04:49.785Z	INFO	loggingexporter/logging_exporter.go:42	TracesExporter	{"#spans": 2}
2022-08-04T12:04:59.789Z	INFO	loggingexporter/logging_exporter.go:42	TracesExporter	{"#spans": 7}
2022-08-04T12:05:04.791Z	INFO	loggingexporter/logging_exporter.go:42	TracesExporter	{"#spans": 7}
2022-08-04T12:05:09.795Z	INFO	loggingexporter/logging_exporter.go:42	TracesExporter	{"#spans": 7}

0 replies

rpancham · 2022-08-05T06:22:18Z

rpancham
Aug 5, 2022
Collaborator Author

oc get pods NAME READY STATUS RESTARTS AGE my-database-949975856-zlcmc 1/1 Running 0 24h nodejs-rest-http-crud-1-deploy 0/1 Completed 0 24h nodejs-rest-http-crud-2-deploy 0/1 Completed 0 24h nodejs-rest-http-crud-3-5glmd 1/1 Running 0 80s nodejs-rest-http-crud-3-deploy 0/1 Completed 0 84s nodejs-rest-http-crud-s2i-10-build 0/1 Error 0 2d nodejs-rest-http-crud-s2i-13-build 0/1 Completed 0 2d nodejs-rest-http-crud-s2i-14-build 0/1 Completed 0 41h nodejs-rest-http-crud-s2i-15-build 0/1 Completed 0 24h nodejs-rest-http-crud-s2i-16-build 0/1 Completed 0 24h nodejs-rest-http-crud-s2i-17-build 0/1 Completed 0 3m15s nodejs-rest-http-crud-s2i-7-build 0/1 Error 0 8d opentel-collector-6774895d5d-kncvs 1/1 Running 0 19h opentel-jaeger-54487774b7-lhrhn 1/1 Running 0 6m43s opentel-jaeger2-c55b8f778-k2vth 2/2 Running 0 24h oc logs opentel-collector-6774895d5d-kncvs 2022-08-04T10:37:41.890Z info builder/exporters_builder.go:255 Exporter was built. {"kind": "exporter", "name": "logging"} 2022-08-04T10:37:41.891Z info builder/exporters_builder.go:255 Exporter was built. {"kind": "exporter", "name": "jaeger"} 2022-08-04T10:37:41.891Z info builder/pipelines_builder.go:224 Pipeline was built. {"kind": "pipeline", "name": "traces"} 2022-08-04T10:37:41.891Z info builder/receivers_builder.go:226 Receiver was built. {"kind": "receiver", "name": "otlp", "datatype": "traces"} 2022-08-04T10:37:41.891Z info service/telemetry.go:108 Setting up own telemetry... 2022-08-04T10:37:41.892Z info service/telemetry.go:128 Serving Prometheus metrics {"address": ":8888", "level": "basic", "service.instance.id": "ce78458b-352d-4290-beb7-b41c2ed5ac62", "service.version": "v0.42.0-9-g0435914"} 2022-08-04T10:37:41.892Z info service/service.go:82 Starting extensions... 2022-08-04T10:37:41.892Z info service/service.go:87 Starting exporters... 2022-08-04T10:37:41.892Z info builder/exporters_builder.go:40 Exporter is starting... {"kind": "exporter", "name": "logging"} 2022-08-04T10:37:41.892Z info builder/exporters_builder.go:48 Exporter started. {"kind": "exporter", "name": "logging"} 2022-08-04T10:37:41.892Z info builder/exporters_builder.go:40 Exporter is starting... {"kind": "exporter", "name": "jaeger"} 2022-08-04T10:37:41.893Z info builder/exporters_builder.go:48 Exporter started. {"kind": "exporter", "name": "jaeger"} 2022-08-04T10:37:41.893Z info service/service.go:92 Starting processors... 2022-08-04T10:37:41.893Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "IDLE"} 2022-08-04T10:37:41.893Z info builder/pipelines_builder.go:54 Pipeline is starting... {"kind": "pipeline", "name": "traces"} 2022-08-04T10:37:41.893Z info builder/pipelines_builder.go:65 Pipeline is started. {"kind": "pipeline", "name": "traces"} 2022-08-04T10:37:41.893Z info service/service.go:97 Starting receivers... 2022-08-04T10:37:41.893Z info builder/receivers_builder.go:68 Receiver is starting... {"kind": "receiver", "name": "otlp"} 2022-08-04T10:37:41.893Z info otlpreceiver/otlp.go:70 Starting GRPC server on endpoint 0.0.0.0:4317 {"kind": "receiver", "name": "otlp"} 2022-08-04T10:37:41.894Z info otlpreceiver/otlp.go:88 Starting HTTP server on endpoint opentel-collector-headless.opentel.svc:4318 {"kind": "receiver", "name": "otlp"} 2022-08-04T10:37:42.894Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "CONNECTING"} 2022-08-04T10:37:46.896Z info builder/receivers_builder.go:73 Receiver started. {"kind": "receiver", "name": "otlp"} 2022-08-04T10:37:46.896Z info service/collector.go:249 Starting otelcol... {"Version": "0.49.0", "NumCPU": 8} 2022-08-04T10:37:46.896Z info service/collector.go:145 Everything is ready. Begin running and processing data. 2022-08-04T10:37:46.972Z warn zapgrpc/zapgrpc.go:191 [core] grpc: addrConn.createTransport failed to connect to {opentel-jaeger-collector-headless.opentel.svc:14250 opentel-jaeger-collector-headless.opentel.svc:14250 <nil> <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp: lookup opentel-jaeger-collector-headless.opentel.svc on 10.217.4.10:53: no such host" {"grpc_log": true} 2022-08-04T10:37:47.894Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "TRANSIENT_FAILURE"} 2022-08-04T10:37:48.894Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "IDLE"}

…

On Thu, Aug 4, 2022 at 5:38 PM Helio Frota ***@***.***> wrote: Could you please run the following command: ❯ oc get pods NAME READY STATUS RESTARTS AGE my-database-949975856-4trbw 1/1 Running 3 47h nodejs-rest-http-crud-1-deploy 1/1 Running 0 15s nodejs-rest-http-crud-1-lq69p 0/1 Running 0 12s nodejs-rest-http-crud-s2i-1-build 0/1 Completed 0 113s opentel-collector-6774895d5d-grdc4 1/1 Running 0 2m7s opentel-jaeger-5b687db5-h4jtm 2/2 Running 2 24h And then run the oc logs for your collector and paste the results here. in my case: oc logs opentel-collector-6774895d5d-grdc4 ❯ oc logs opentel-collector-6774895d5d-grdc4 2022-08-04T12:02:51.690Z info builder/exporters_builder.go:255 Exporter was built. {"kind": "exporter", "name": "logging"} 2022-08-04T12:02:51.690Z info builder/exporters_builder.go:255 Exporter was built. {"kind": "exporter", "name": "jaeger"} 2022-08-04T12:02:51.690Z info builder/pipelines_builder.go:224 Pipeline was built. {"kind": "pipeline", "name": "traces"} 2022-08-04T12:02:51.690Z info builder/receivers_builder.go:226 Receiver was built. {"kind": "receiver", "name": "otlp", "datatype": "traces"} 2022-08-04T12:02:51.690Z info service/telemetry.go:108 Setting up own telemetry... 2022-08-04T12:02:51.692Z info service/telemetry.go:128 Serving Prometheus metrics {"address": ":8888", "level": "basic", "service.instance.id": "c7034d1a-4ede-4975-ab4a-fec104c19b09", "service.version": "v0.42.0-9-g0435914"} 2022-08-04T12:02:51.692Z info service/service.go:82 Starting extensions... 2022-08-04T12:02:51.692Z info service/service.go:87 Starting exporters... 2022-08-04T12:02:51.692Z info builder/exporters_builder.go:40 Exporter is starting... {"kind": "exporter", "name": "logging"} 2022-08-04T12:02:51.692Z info builder/exporters_builder.go:48 Exporter started. {"kind": "exporter", "name": "logging"} 2022-08-04T12:02:51.692Z info builder/exporters_builder.go:40 Exporter is starting... {"kind": "exporter", "name": "jaeger"} 2022-08-04T12:02:51.692Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "IDLE"} 2022-08-04T12:02:51.692Z info builder/exporters_builder.go:48 Exporter started. {"kind": "exporter", "name": "jaeger"} 2022-08-04T12:02:51.692Z info service/service.go:92 Starting processors... 2022-08-04T12:02:51.692Z info builder/pipelines_builder.go:54 Pipeline is starting... {"kind": "pipeline", "name": "traces"} 2022-08-04T12:02:51.692Z info builder/pipelines_builder.go:65 Pipeline is started. {"kind": "pipeline", "name": "traces"} 2022-08-04T12:02:51.692Z info service/service.go:97 Starting receivers... 2022-08-04T12:02:51.692Z info builder/receivers_builder.go:68 Receiver is starting... {"kind": "receiver", "name": "otlp"} 2022-08-04T12:02:51.692Z info otlpreceiver/otlp.go:70 Starting GRPC server on endpoint 0.0.0.0:4317 {"kind": "receiver", "name": "otlp"} 2022-08-04T12:02:51.692Z info otlpreceiver/otlp.go:88 Starting HTTP server on endpoint opentel-collector-headless.opentel.svc:4318 {"kind": "receiver", "name": "otlp"} 2022-08-04T12:02:52.692Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "CONNECTING"} 2022-08-04T12:02:56.694Z info builder/receivers_builder.go:73 Receiver started. {"kind": "receiver", "name": "otlp"} 2022-08-04T12:02:56.694Z info service/collector.go:249 Starting otelcol... {"Version": "0.49.0", "NumCPU": 8} 2022-08-04T12:02:56.694Z info service/collector.go:145 Everything is ready. Begin running and processing data. 2022-08-04T12:02:57.692Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "READY"} 2022-08-04T12:04:49.785Z INFO loggingexporter/logging_exporter.go:42 TracesExporter {"#spans": 2} 2022-08-04T12:04:59.789Z INFO loggingexporter/logging_exporter.go:42 TracesExporter {"#spans": 7} 2022-08-04T12:05:04.791Z INFO loggingexporter/logging_exporter.go:42 TracesExporter {"#spans": 7} 2022-08-04T12:05:09.795Z INFO loggingexporter/logging_exporter.go:42 TracesExporter {"#spans": 7} — Reply to this email directly, view it on GitHub <#348 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW2BEK6C7ZGEXBJZXXK5P33VXOXEFANCNFSM55K2CFJA> . You are receiving this because you were mentioned.Message ID: <nodeshift-starters/nodejs-rest-http-crud/repo-discussions/348/comments/3324823 @github.com>

1 reply

helio-frota Aug 5, 2022
Maintainer

Thanks for the logs.

As you can see you have 2 Jaeger running:

opentel-collector-6774895d5d-kncvs   1/1     Running     0          19h
opentel-jaeger-54487774b7-lhrhn      1/1     Running     0          6m43s
opentel-jaeger2-c55b8f778-k2vth      2/2     Running     0          24h

I suggest you to delete the 2 jaeger and also the opentelemetry collector, because for some reason jager must be available before opentelemetry collector.

You can use command line to delete if you want to

$ oc delete opentelemetrycollector opentel
$ oc delete jaeger opentel-jaeger
$ oc delete jaeger opentel-jaeger2
$ oc delete cm opentel-cabundle    # (also good to delete the config map to test)

The other log is showing extra information. It seems that

[ opentelemetry-collector ] --- can not communicate with --> [ jager ]

Err: connection error: desc = "transport: Error while dialing dial tcp:
lookup opentel-jaeger-collector-headless.opentel.svc on 10.217.4.10:53: no
such host" {"grpc_log": true}
2022-08-04T10:37:47.894Z info ***@***.***/exporter.go:186 State
of the connection with the Jaeger Collector backend {"kind": "exporter",
"name": "jaeger", "state": "TRANSIENT_FAILURE"}

rpancham · 2022-08-05T11:44:51Z

rpancham
Aug 5, 2022
Collaborator Author

OKay Helio Deleted and created the instances again

…

On Fri, Aug 5, 2022 at 4:58 PM Helio Frota ***@***.***> wrote: Thanks for the logs. As you can see you have 2 Jaeger running: opentel-collector-6774895d5d-kncvs 1/1 Running 0 19h opentel-jaeger-54487774b7-lhrhn 1/1 Running 0 6m43s opentel-jaeger2-c55b8f778-k2vth 2/2 Running 0 24h I suggest you to delete the 2 jaeger and also the opentelemetry collector, because for some reason jager must be available before opentelemetry collector. You can use command line to delete if you want to $ oc delete opentelemetrycollector opentel $ oc delete jaeger opentel-jaeger $ oc delete jaeger opentel-jaeger2 $ oc delete cm opentel-cabundle # (also good to delete the config map to test) The other log is showing extra information. It seems that [ opentelemetry-collector ] --- can not communicate with --> [ jager ] Err: connection error: desc = "transport: Error while dialing dial tcp: lookup opentel-jaeger-collector-headless.opentel.svc on 10.217.4.10:53: no such host" {"grpc_log": true} 2022-08-04T10:37:47.894Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "TRANSIENT_FAILURE"} — Reply to this email directly, view it on GitHub <#348 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW2BEK335LZKYJ3YU4IB4YTVXT3EBANCNFSM55K2CFJA> . You are receiving this because you were mentioned.Message ID: <nodeshift-starters/nodejs-rest-http-crud/repo-discussions/348/comments/3332846 @github.com>

1 reply

helio-frota Aug 5, 2022
Maintainer

Please run the same commands and share the logs 👍

rpancham · 2022-08-05T11:53:16Z

rpancham
Aug 5, 2022
Collaborator Author

oc get pods NAME READY STATUS RESTARTS AGE my-database-949975856-zlcmc 1/1 Running 0 30h nodejs-rest-http-crud-3-deploy 0/1 Completed 0 5h38m nodejs-rest-http-crud-4-deploy 0/1 Completed 0 4h45m nodejs-rest-http-crud-5-26bsq 1/1 Running 0 10m nodejs-rest-http-crud-5-deploy 0/1 Completed 0 10m nodejs-rest-http-crud-s2i-10-build 0/1 Error 0 2d6h nodejs-rest-http-crud-s2i-15-build 0/1 Completed 0 30h nodejs-rest-http-crud-s2i-16-build 0/1 Completed 0 29h nodejs-rest-http-crud-s2i-17-build 0/1 Completed 0 5h40m nodejs-rest-http-crud-s2i-18-build 0/1 Completed 0 4h47m nodejs-rest-http-crud-s2i-19-build 0/1 Completed 0 12m nodejs-rest-http-crud-s2i-7-build 0/1 Error 0 9d opentel-collector-6774895d5d-7clkl 1/1 Running 0 8m35s opentel-jaeger-77885c59bb-5wjvx 2/2 Running 0 8m51s oc logs opentel-collector-6774895d5d-7clkl 2022-08-05T11:41:22.938Z info builder/exporters_builder.go:255 Exporter was built. {"kind": "exporter", "name": "jaeger"} 2022-08-05T11:41:22.939Z info builder/exporters_builder.go:255 Exporter was built. {"kind": "exporter", "name": "logging"} 2022-08-05T11:41:22.939Z info builder/pipelines_builder.go:224 Pipeline was built. {"kind": "pipeline", "name": "traces"} 2022-08-05T11:41:22.940Z info builder/receivers_builder.go:226 Receiver was built. {"kind": "receiver", "name": "otlp", "datatype": "traces"} 2022-08-05T11:41:22.940Z info service/telemetry.go:108 Setting up own telemetry... 2022-08-05T11:41:22.941Z info service/telemetry.go:128 Serving Prometheus metrics {"address": ":8888", "level": "basic", "service.instance.id": "59c69250-1bf3-4b10-a029-68161ba7940c", "service.version": "v0.42.0-9-g0435914"} 2022-08-05T11:41:22.941Z info service/service.go:82 Starting extensions... 2022-08-05T11:41:22.941Z info service/service.go:87 Starting exporters... 2022-08-05T11:41:22.941Z info builder/exporters_builder.go:40 Exporter is starting... {"kind": "exporter", "name": "jaeger"} 2022-08-05T11:41:22.942Z info builder/exporters_builder.go:48 Exporter started. {"kind": "exporter", "name": "jaeger"} 2022-08-05T11:41:22.942Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "IDLE"} 2022-08-05T11:41:22.942Z info builder/exporters_builder.go:40 Exporter is starting... {"kind": "exporter", "name": "logging"} 2022-08-05T11:41:22.942Z info builder/exporters_builder.go:48 Exporter started. {"kind": "exporter", "name": "logging"} 2022-08-05T11:41:22.942Z info service/service.go:92 Starting processors... 2022-08-05T11:41:22.942Z info builder/pipelines_builder.go:54 Pipeline is starting... {"kind": "pipeline", "name": "traces"} 2022-08-05T11:41:22.942Z info builder/pipelines_builder.go:65 Pipeline is started. {"kind": "pipeline", "name": "traces"} 2022-08-05T11:41:22.942Z info service/service.go:97 Starting receivers... 2022-08-05T11:41:22.942Z info builder/receivers_builder.go:68 Receiver is starting... {"kind": "receiver", "name": "otlp"} 2022-08-05T11:41:22.942Z info otlpreceiver/otlp.go:70 Starting GRPC server on endpoint 0.0.0.0:4317 {"kind": "receiver", "name": "otlp"} 2022-08-05T11:41:22.942Z info otlpreceiver/otlp.go:88 Starting HTTP server on endpoint opentel-collector-headless.opentel.svc:4318 {"kind": "receiver", "name": "otlp"} 2022-08-05T11:41:23.942Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "CONNECTING"} 2022-08-05T11:41:27.945Z info builder/receivers_builder.go:73 Receiver started. {"kind": "receiver", "name": "otlp"} 2022-08-05T11:41:27.945Z info service/collector.go:249 Starting otelcol... {"Version": "0.49.0", "NumCPU": 8} 2022-08-05T11:41:27.945Z info service/collector.go:145 Everything is ready. Begin running and processing data. 2022-08-05T11:41:28.943Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "READY"}

…

On Fri, Aug 5, 2022 at 5:17 PM Helio Frota ***@***.***> wrote: Please run the same commands and share the logs 👍 — Reply to this email directly, view it on GitHub <#348 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW2BEK6JLNU2IUKIAEFV2KLVXT5OPANCNFSM55K2CFJA> . You are receiving this because you were mentioned.Message ID: <nodeshift-starters/nodejs-rest-http-crud/repo-discussions/348/comments/3332951 @github.com>

1 reply

helio-frota Aug 5, 2022
Maintainer

Looks like everything is working now

2022-08-05T11:41:28.943Z info ***@***.***/exporter.go:186 State
of the connection with the Jaeger Collector backend {"kind": "exporter",
"name": "jaeger", "state": "READY"}

Can you please access the app, do some operations, and then go to the jaeger and I think it will show the traces

rpancham · 2022-08-05T12:18:35Z

rpancham
Aug 5, 2022
Collaborator Author

Thanks @helio Frota . It's working now.

…

On Fri, Aug 5, 2022 at 5:26 PM Helio Frota ***@***.***> wrote: Looks like everything is working now 2022-08-05T11:41:28.943Z info ***@***.***/exporter.go:186 State of the connection with the Jaeger Collector backend {"kind": "exporter", "name": "jaeger", "state": "READY"} Can you please access the app, do some operations, and then go to the jaeger and I think it will show the traces — Reply to this email directly, view it on GitHub <#348 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AW2BEK7QUUK6B6CWLUNQJ6TVXT6ORANCNFSM55K2CFJA> . You are receiving this because you were mentioned.Message ID: <nodeshift-starters/nodejs-rest-http-crud/repo-discussions/348/comments/3333007 @github.com>

1 reply

helio-frota Aug 5, 2022
Maintainer

Great 🎉

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Facing the issue after runnig the Jaeger UI #348

{{title}}

Replies: 14 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Facing the issue after runnig the Jaeger UI #348

rpancham Aug 2, 2022 Collaborator

Replies: 14 comments · 5 replies

helio-frota Aug 2, 2022 Maintainer

helio-frota Aug 2, 2022 Maintainer

helio-frota Aug 2, 2022 Maintainer

rpancham Aug 3, 2022 Collaborator Author

helio-frota Aug 3, 2022 Maintainer

helio-frota Aug 3, 2022 Maintainer

rpancham Aug 3, 2022 Collaborator Author

rpancham Aug 3, 2022 Collaborator Author

helio-frota Aug 3, 2022 Maintainer

rpancham Aug 4, 2022 Collaborator Author

helio-frota Aug 4, 2022 Maintainer

rpancham Aug 5, 2022 Collaborator Author

helio-frota Aug 5, 2022 Maintainer

rpancham Aug 5, 2022 Collaborator Author

helio-frota Aug 5, 2022 Maintainer

rpancham Aug 5, 2022 Collaborator Author

helio-frota Aug 5, 2022 Maintainer

rpancham Aug 5, 2022 Collaborator Author

helio-frota Aug 5, 2022 Maintainer

rpancham
Aug 2, 2022
Collaborator

Replies: 14 comments 5 replies

helio-frota
Aug 2, 2022
Maintainer

helio-frota
Aug 2, 2022
Maintainer

helio-frota
Aug 2, 2022
Maintainer

rpancham
Aug 3, 2022
Collaborator Author

helio-frota
Aug 3, 2022
Maintainer

helio-frota
Aug 3, 2022
Maintainer

rpancham
Aug 3, 2022
Collaborator Author

rpancham
Aug 3, 2022
Collaborator Author

helio-frota
Aug 3, 2022
Maintainer

rpancham Aug 4, 2022
Collaborator Author

helio-frota
Aug 4, 2022
Maintainer

rpancham
Aug 5, 2022
Collaborator Author

helio-frota Aug 5, 2022
Maintainer

rpancham
Aug 5, 2022
Collaborator Author

helio-frota Aug 5, 2022
Maintainer

rpancham
Aug 5, 2022
Collaborator Author

helio-frota Aug 5, 2022
Maintainer

rpancham
Aug 5, 2022
Collaborator Author

helio-frota Aug 5, 2022
Maintainer