proxy.golang.org : github.com/xoplog/xopotel-go
Package xopotel provides a gateways between XOP and Open Telemetry. There is a mismatch of features between Open Telemetry and XOP. Open Telemetry supports only a very limited set of attribute types. When gatewaying from XOP into Open Telemetry the richer set of types are almost always converted to string slices. There are several integration points. The BaseLogger() function returns a xopbase.Logger that can be used like any other base logger to configure XOP output. In this case, the XOP logs and traces will be output through the Open Telemtry system using the primary interfaces of TracerProvider, Tracer, Span, etc. There is a restriction though: to use this you MUST create the TracerProvider with the xopotel IDGenerator: This allows the TraceIDs and SpanIDs created by XOP to be used by Open Telemetry. If for some reason, you do not have control over the creation of your TracerProvider, you can use SeedModifer() modify your xop.Seed so that it delgates SpanID and TraceID creation to Open Telemetry. If you don't have access to a TracerProvider at all and instead have a "go.opentelemetry.io/otel/trace".Span, you can use that as the basis for generating logs with XOP by converting it directly to a *xop.Logger. BufferedReplayLogger creates a fresh TracerProvider and Tracer for each XOP Request. It offeres the higher quality translation from XOP into OTEL but at a cost: all data relating to each Request is fully buffered in memory before the TracerProvider and Tracer are crated. There is no output until the Request is complete. BufferedReplayLogger is meant for the situation where another xopbase.Logger is being replayed into xopotel. It is also the only way to losslessly round trip OTEL logs to XOP and then back to OTEL. BufferedReplayExporterWrapper augments BufferedReplayLogger by passing information around the OTEL TracerProvider, Tracer, and Span. When not using it, Scope.Name, and all the counters that ReadOnlySpan provides are lost. Integration can go the other direction. You can flow traces from Open Telemetry to XOP base loggers. Use ExportToXOP() to wrap a xopbase.Logger so that it can be used as a SpanExporter. Ideally, it should be possible to run data in a round trip from XOP to OTEL back to XOP and have it unchanged and also run data from OTEL to XOP and back to OTEL and have it unchanged. The former (XOP -> OTEL -> XOP) works. Unfortunately, OTEL -> XOP -> OTEL is difficult to get working and only fully works when using the BufferedReplayLogger and the BufferedReplayExporterWrapper. This complexity could be avoided if it were possible for others to implement ReadOnlySpan.
Registry
-
Source
- Documentation
- JSON
purl: pkg:golang/github.com/xoplog/xopotel-go
License: MIT
Latest release: over 1 year ago
First release: over 1 year ago
Namespace: github.com/xoplog
Stars: 0 on GitHub
Forks: 0 on GitHub
See more repository details: repos.ecosyste.ms
Last synced: 3 days ago