OpenObserve Configuration Issue with OTEL Collector
TLDRShashank has issues with running openobserve v0.5.0 and OTEL collector(v0.80.0) due to an error in the traces pipeline. Prabhat suggested to modify the API endpoint.
Shashank
Wed, 19 Jul 2023 07:14:47 UTC
Hi Team, I have configured openobserve v0.5.0 along with OTEL collector(v0.80.0) with below configuration. But I am facing issue in traces pipeline. OTEL collector is continuously throwing this error:
```2023-07-19T12:40:03.628+0530 info zapgrpc/zapgrpc.go:178 [core] [Channel #1 SubChannel #2] Subchannel picks a new address "localhost:5080/api/default/traces" to connect {"grpc_log": true} 2023-07-19T12:40:03.628+0530 info zapgrpc/zapgrpc.go:178 [core] Creating new client transport to "{Addr: \"localhost:5080/api/default/traces\", ServerName: \"localhost:5080/api/default/traces\", }": connection error: desc = "transport: Error while dialing: dial tcp: address tcp/5080/api/default/traces: unknown port" {"grpc_log": true} 2023-07-19T12:40:03.628+0530 warn zapgrpc/zapgrpc.go:195 [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "localhost:5080/api/default/traces", ServerName: "localhost:5080/api/default/traces", }. Err: connection error: desc = "transport: Error while dialing: dial tcp: address tcp/5080/api/default/traces: unknown port" ```
OTEL config:
```receivers:
otlp:
protocols:
grpc:
http:
processors:
attributes/insert:
actions:
- key: ENVIRONMENT
value: dev-shashank-traces
action: insert
- key: CLUSTER_ID
value: dev-mdm
action: insert
- key: PROJECT_NAME
value: Observability Framework
action: insert
- key: BUILD_VERSION
value: Observability-v1.0.0-d1c19
action: insert
batch:
filter/body:
logs:
exclude:
match_type: regexp
bodies:
- ".*/health"
- ".*/healthz"
memory_limiter:
limit_percentage: 85
check_interval: 1s
spike_limit_percentage: 10
exporters:
otlp:
endpoint:
headers:
Authorization: Basic cm9vdEBle********3YzlmMUI3ZTBFNzZS
pipelines:
traces:
receivers:
- otlp
processors:
- attributes/insert
exporters:
- otlp```
Can someone please help me with the scenario ??
Prabhat
Wed, 19 Jul 2023 13:24:27 UTC
Can you try the API endpoint as just
``` ```
OpenObserve
Indexed 419 threads
OpenObserve is an open-source, petabyte-scale observability platform for the cloud native realm, offering a 10x cost reduction and 140x less storage use compared to competitors like Elasticsearch or Splunk. Built in Rust for exceptional performance, it offers comprehensive features like logs, metrics, traces, dashboards, and more | Knowledge Base powered by Struct.AI
Shashank
Wed, 19 Jul 2023 07:14:47 UTCHi Team, I have configured openobserve v0.5.0 along with OTEL collector(v0.80.0) with below configuration. But I am facing issue in traces pipeline. OTEL collector is continuously throwing this error: ```2023-07-19T12:40:03.628+0530 info zapgrpc/zapgrpc.go:178 [core] [Channel #1 SubChannel #2] Subchannel picks a new address "localhost:5080/api/default/traces" to connect {"grpc_log": true} 2023-07-19T12:40:03.628+0530 info zapgrpc/zapgrpc.go:178 [core] Creating new client transport to "{Addr: \"localhost:5080/api/default/traces\", ServerName: \"localhost:5080/api/default/traces\", }": connection error: desc = "transport: Error while dialing: dial tcp: address tcp/5080/api/default/traces: unknown port" {"grpc_log": true} 2023-07-19T12:40:03.628+0530 warn zapgrpc/zapgrpc.go:195 [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "localhost:5080/api/default/traces", ServerName: "localhost:5080/api/default/traces", }. Err: connection error: desc = "transport: Error while dialing: dial tcp: address tcp/5080/api/default/traces: unknown port" ``` OTEL config: ```receivers: otlp: protocols: grpc: http: processors: attributes/insert: actions: - key: ENVIRONMENT value: dev-shashank-traces action: insert - key: CLUSTER_ID value: dev-mdm action: insert - key: PROJECT_NAME value: Observability Framework action: insert - key: BUILD_VERSION value: Observability-v1.0.0-d1c19 action: insert batch: filter/body: logs: exclude: match_type: regexp bodies: - ".*/health" - ".*/healthz" memory_limiter: limit_percentage: 85 check_interval: 1s spike_limit_percentage: 10 exporters: otlp: endpoint:
headers:
Authorization: Basic cm9vdEBle********3YzlmMUI3ZTBFNzZS
pipelines:
traces:
receivers:
- otlp
processors:
- attributes/insert
exporters:
- otlp```
Can someone please help me with the scenario ??