otel-launcher-go icon indicating copy to clipboard operation
otel-launcher-go copied to clipboard

Launcher, a Lightstep Distro for OpenTelemetry Go 🚀

Results 80 otel-launcher-go issues
Sort by recently updated
recently updated
newest added

**Description:** These three error conditions, when they occur, are likely to be frequent. By using `doevery`, we avoid repetitive logging of these conditions. **Link to tracking Issue:** Fixes #271. **Testing:**...

**Is your feature request related to a problem? Please describe.** When a user of the Metrics SDK uses NaN, Inf values, or for Histogram and Counter instruments negative values, the...

**Is your feature request related to a problem? Please describe.** The builtin metrics provided by this library are out-of-date with respect to the OTel specifications and with respect to the...

**Description:** The go-contrib instrumentation/host package features several process-level metrics. These are candidates for inclusion in the runtime package and are candidates for the Golang runtime/metrics package to produce. Therefore, they...

**Description:** Produces process.cpu.time metrics, formerly produced by the go-contrib instrumentation/host package. This is not host instrumentation, could become runtime instrumentation. - Use of syscall.Getrusage directly as opposed to gopsutil/v3/cpu/process, -...

**Description:** Lightstep had added custom handling for non-standard response headers; this is now standardized. Our special support can be removed ~after https://github.com/open-telemetry/opentelemetry-go/pull/3106 merges~. **EDIT: This is stalled until an OTel-Go...

dependencies

**Is your feature request related to a problem? Please describe.** Because a single interval computes a single protocol message, there is no current feature allowing users to place limits on...

**Describe the bug** See https://github.com/golang/go/issues/54302 **To Reproduce** Use Go-1.19 and this code, specifically the lighstep/sdk/metric/aggregator/minmaxsumcount package appears to trigger the compiler and we're yet sure how. **Expected behavior** This should...

As per the specification https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md#opentelemetry-protocol-exporter, the environment variable is TRACES, not SPAN.

As per the specification https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md#opentelemetry-protocol-exporter, the environment variable is plural.