-
Hello,
I am trying to replace signalfx smart agent by otel collector since its deprecation.
I started with a simple configuration for host, kubernetes and nginx metrics.
```
exporters:
sa…
-
**Describe the bug**
data race in batch processor and kafkareceiver
```
==================
WARNING: DATA RACE
Write at 0x00c0001108d0 by goroutine 115:
go.opentelemetry.io/collector/consumer…
hanjm updated
3 years ago
-
**Description**
That is the first piece to solve https://github.com/kyma-project/kyma/issues/10119
Motivation:
- build up knowledge and understanding of the architecture of the OTEL compo…
-
**Describe the bug**
The OTLP/HTTP OTEP states:
> Response body for all `HTTP 4xx` and `HTTP 5xx` responses MUST be a ProtoBuf-encoded [Status](https://godoc.org/google.golang.org/genproto/googleapi…
-
After coding the 3 core extensions (health-check, pprof, zPages) it become clear that the code for them is very similar and can be refactored to reduced code repetition. The one that is slightly diffe…
-
**Describe the bug**
otle-collector crashes on startup
**Steps to reproduce**
If possible, provide a recipe for reproducing the error.
**What did you expect to see?**
No crash on startup :)
…
-
**Describe the bug**
I'm playing around with setting up opentelemetry with Jaeger for the first time, and Jaeger is spewing errors. They look like this:
> {"level":"error","ts":1592618224.399752,"…
nicks updated
3 years ago
-
**Describe the bug**
Crash on startup after adding collector:
```
k8s_cluster:
auth_type: "serviceAccount"
collection_interval: 10s
node_conditions_to_report: [Re…
-
## In what area(s)?
/area observability
## Related issue
dapr/dapr#969
## Describe the feature
When we improve traces (#969), it is good to provide monitoring images or helm charts with…
-
**Describe the bug**
Jaeger gRPC receiver doesn't work properly
**Steps to reproduce**
I'm using the collector as agent to Jaeger HTTP Thrift endpoint. I'm connecting from opentelemetry client se…