-
i have the following configuration for my otel collector
```yaml
extensions:
health_check:
pprof:
endpoint: 0.0.0.0:1777
zpages:
endpoint: 0.0.0.0:55679
receivers:
otlp:
…
-
### Description of the problem / feature request:
Bug - bazel running a go build, once interrupted(signal shut down- syscall.SIGINT) does not shut down the process. Lingering java process remains.…
-
**Describe the bug**
After a while the pod, on which the collector runs, stops with this error:
```
panic: runtime error: slice bounds out of range [-2:]
32
31
goroutine 137 [running]:
30
go…
-
**Describe the bug**
While k8sattributesprocessor correctly adds pod attributes to pods that exist when the collector is started, restarting a pod causes the processor to no longer add attributes
…
-
### What happened?
## Description
1、I want to use opentelemetry skywalking-receiver and otlp-exporter report trace
2、use java to impl [opentelemetry collector proto](https://github.com/open-tel…
-
**Steps to reproduce**
docker run --privileged -p 7276:7276 -p 8888:8888 -p 9943:9943 -p 55679:55679 -p 55680:55680 -p 9411:9411 -v $(pwd)/config.yaml:/etc/otel-contrib-collector/config.yaml --name l…
itsif updated
2 years ago
-
**What happened**:
`../v1/frontendservice/tickets/{TICKET_ID}/assignments` is an endless call.
When I browse logs at the k8s pod, I see these errors:
#### Director service
```
←[41m←[30mfail←…
-
splunk-otel-agent raise error:
Post http://splunk-otel:9943/v2/datapoint context deadline exceeded (Client.Timeout exceeded while awaiting headers)
```
2022-09-22T11:04:56.275Z error exporterh…
-
I Have installed the opentelemetry-collector-contrib as windows service here is the configuration file .
# # receivers:
# # otlp:
# # protocols:
# # grpc:
# # http:
# # pro…
-
```
receivers:
prometheus:
config:
global:
scrape_interval: 15s
scrape_timeout: 10s
scrape_configs:
- job_name: consul
metrics_path: /metri…