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

Supportability: Revisit the log entries we have #2431

Closed
jpkrohling opened this issue Feb 2, 2021 · 2 comments
Closed

Supportability: Revisit the log entries we have #2431

jpkrohling opened this issue Feb 2, 2021 · 2 comments

Comments

@jpkrohling
Copy link
Member

Context: #2098 (comment)

This issue here is to track which log entries we have in the usual case, which ones are shown when a problem happens, and what we could be having to help identify problems.

@jpkrohling
Copy link
Member Author

When the logging exporter is enabled with logLevel: debug, the following is seen when a batch with 2 spans is sent and the pipeline is properly configured:

2021-02-02T13:24:36.255+0100	INFO	loggingexporter/logging_exporter.go:313	TracesExporter	{"#spans": 2}
2021-02-02T13:24:36.255+0100	DEBUG	loggingexporter/logging_exporter.go:352	ResourceSpans #0
Resource labels:
     -> service.name: STRING(tracegen)
InstrumentationLibrarySpans #0
InstrumentationLibrary tracegen 
Span #0
    Trace ID       : 2cdd9ff21dc834d442d4762e8cffef12
    Parent ID      : 163337910d2306b2
    ID             : f2d897eeeb45c938
    Name           : okey-dokey
    Kind           : SPAN_KIND_INTERNAL
    Start time     : 2021-02-02 13:24:36.25349814 +0100 CET
    End time       : 2021-02-02 13:24:36.253622118 +0100 CET
    Status code    : STATUS_CODE_OK
    Status message : 
Attributes:
     -> span.kind: STRING(server)
     -> net.peer.ip: STRING(1.2.3.4)
     -> peer.service: STRING(tracegen-client)
Span #1
    Trace ID       : 2cdd9ff21dc834d442d4762e8cffef12
    Parent ID      : 
    ID             : 163337910d2306b2
    Name           : lets-go
    Kind           : SPAN_KIND_INTERNAL
    Start time     : 2021-02-02 13:24:36.253494558 +0100 CET
    End time       : 2021-02-02 13:24:36.253622118 +0100 CET
    Status code    : STATUS_CODE_OK
    Status message : 
Attributes:
     -> span.kind: STRING(client)
     -> net.peer.ip: STRING(1.2.3.4)
     -> peer.service: STRING(tracegen-server)

@jpkrohling
Copy link
Member Author

When using the Jaeger exporter and the remote backend isn't available, the following can be seen in the default configuration:

2021-02-02T13:40:44.298+0100	INFO	jaegerexporter/exporter.go:190	State of the connection with the Jaeger Collector backend	{"component_kind": "exporter", "component_type": "jaeger", "component_name": "jaeger", "state": "TRANSIENT_FAILURE"}
2021-02-02T13:40:49.424+0100	INFO	exporterhelper/queued_retry.go:276	Exporting failed. Will retry the request after interval.	{"component_kind": "exporter", "component_type": "jaeger", "component_name": "jaeger", "error": "failed to push trace data via Jaeger exporter: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp [::1]:14250: connect: connection refused\"", "interval": "5.52330144s"}

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

No branches or pull requests

2 participants