OpenTelemetry Collector未将数据导出到OTEL/HTTP导出器。

huangapple
go评论94阅读模式
英文:

OpenTelemetry Collector not exporting data to OTEL/HTTP exporter

问题

I am using the example from here

https://github.com/open-telemetry/opentelemetry-java-docs/tree/main/otlp/docker

I have modified the OTEL config and now it looks like this. I have added otelhttp and otel exporter configuration.

OTEL Configuration

  1. receivers:
  2.   otlp:
  3.     protocols:
  4.         grpc:
  6. exporters:
  7.   otlp:
  8.     endpoint: "http://docker.for.mac.localhost:4318"
  9.     tls:
  10.       insecure: true
  11.     headers: 
  12.       Authorization: "Basic YWRtaW46YWRtaW4="
  13.       X-P-Stream: "demo"
  14.       X-P-TAG-tag1: "value1"
  15.       X-P-META-meta1: "value1"
  16.       Content-type: "application/json"
  17.   otlphttp:
  18.     endpoint: "http://docker.for.mac.localhost:4318"
  19.     tls:
  20.       insecure: true
  21.     headers: 
  22.       Authorization: "Basic YWRtaW46YWRtaW4="
  23.       X-P-Stream: "demo"
  24.       X-P-TAG-tag1: "value1"
  25.       X-P-META-meta1: "value1"
  26.       Content-type: "application/json"
  27.   prometheus:
  28.     endpoint: "0.0.0.0:8889"
  29.     namespace: promexample
  30.     const_labels:
  31.       label1: value1
  32.   logging:
  33.     loglevel: debug
  35.   zipkin:
  36.     endpoint: "http://zipkin-all-in-one:9411/api/v2/spans"
  37.     format: proto
  39.   jaeger:
  40.     endpoint: jaeger-all-in-one:14250
  41.     tls:
  42.       insecure: true
  44. # Alternatively, use jaeger_thrift_http with the settings below. In this case
  45. # update the list of exporters on the traces pipeline.
  46. #
  47. #  jaeger_thrift_http:
  48. #    url: http://jaeger-all-in-one:14268/api/traces
  50. processors:
  51.   batch:
  53. extensions:
  54.   health_check:
  55.   pprof:
  56.     endpoint: :1888
  57.   zpages:
  58.     endpoint: :55679
  60. service:
  61.   extensions: [pprof, zpages, health_check]
  62.   pipelines:
  63.     traces:
  64.       receivers: [otlp]
  65.       processors: [batch]
  66.       exporters: [logging, zipkin, jaeger, otlp, otlphttp]
  67.     metrics:
  68.       receivers: [otlp]
  69.       processors: [batch]
  70.       exporters: [logging, prometheus, otlp, otlphttp]

and I have a exporter running at port 4318 on localhost and OTEL setup is deployed using docker-compose using below docker compose file

Docker Compose

  1. version: "2"
  2. services:
  4.   # Jaeger
  5.   jaeger-all-in-one:
  6.     image: jaegertracing/all-in-one:latest
  7.     ports:
  8.       - "16686:16686"
  9.       - "14268"
  10.       - "14250:14250"
  12.   # Zipkin
  13.   zipkin-all-in-one:
  14.     image: openzipkin/zipkin:latest
  15.     ports:
  16.       - "9411:9411"
  18.   # Collector
  19.   otel-collector:
  20.     image: ${OTELCOL_IMG}
  21.     command: ["--config=/etc/otel-collector-config-demo.yaml", "${OTELCOL_ARGS}"]
  22.     volumes:
  23.       - ./otel-collector-config-demo.yaml:/etc/otel-collector-config-demo.yaml
  24.     ports:
  25.       - "1888:1888"   # pprof extension
  26.       - "8888:8888"   # Prometheus metrics exposed by the collector
  27.       - "8889:8889"   # Prometheus exporter metrics
  28.       - "13133:13133" # health_check extension
  29.       - "55679:55679" # zpages extension
  30.       - "4317:4317"   # otlp receiver
  31.       - "8000:8000"   # parseable exporter
  32.       - "4318:4318"
  33.     depends_on:
  34.       - jaeger-all-in-one
  35.       - zipkin-all-in-one
  36.     environment:
  37.       OTEL_EXPORTER_OTLP_ENDPOINT: http://docker.for.mac.localhost:4318
  39.   prometheus:
  40.     container_name: prometheus
  41.     image: prom/prometheus:latest
  42.     volumes:
  43.       - ./prometheus.yaml:/etc/prometheus/prometheus.yml
  44.     ports:
  45.       - "9090:9090"

On exporter side

(written in Rust) I am seeing this error

  1. [2023-06-01T22:29:27Z ERROR actix_http::h1::dispatcher] stream error: Request parse error: Invalid HTTP version specified
  2. [2023-06-01T22:29:27Z ERROR actix_http::h1::dispatcher] stream error: Request parse error: Invalid HTTP version specified

On OTEL Collector side

I am seeing these errors

  1. 2023-06-01 23:
  3. <details>
  4. <summary>英文:</summary>
  6. I am using the example from here
  8. https://github.com/open-telemetry/opentelemetry-java-docs/tree/main/otlp/docker
  10. I have modified the OTEL config and now it looks like this. I have added otelhttp and otel exporter configuration.
  12. ## OTEL Configuration

receivers:
otlp:
protocols:
grpc:

exporters:
otlp:
endpoint: "http://docker.for.mac.localhost:4318"
tls:
insecure: true
headers:
Authorization: "Basic YWRtaW46YWRtaW4="
X-P-Stream: "demo"
X-P-TAG-tag1: "value1"
X-P-META-meta1: "value1"
Content-type: "application/json"
otlphttp:
endpoint: "http://docker.for.mac.localhost:4318"
tls:
insecure: true
headers:
Authorization: "Basic YWRtaW46YWRtaW4="
X-P-Stream: "demo"
X-P-TAG-tag1: "value1"
X-P-META-meta1: "value1"
Content-type: "application/json"
prometheus:
endpoint: "0.0.0.0:8889"
namespace: promexample
const_labels:
label1: value1
logging:
loglevel: debug

zipkin:
endpoint: "http://zipkin-all-in-one:9411/api/v2/spans"
format: proto

jaeger:
endpoint: jaeger-all-in-one:14250
tls:
insecure: true

Alternatively, use jaeger_thrift_http with the settings below. In this case

update the list of exporters on the traces pipeline.

jaeger_thrift_http:

url: http://jaeger-all-in-one:14268/api/traces

processors:
batch:

extensions:
health_check:
pprof:
endpoint: :1888
zpages:
endpoint: :55679

service:
extensions: [pprof, zpages, health_check]
pipelines:
traces:
receivers: [otlp]
processors: [batch]
exporters: [logging, zipkin, jaeger, otlp, otlphttp]
metrics:
receivers: [otlp]
processors: [batch]
exporters: [logging, prometheus, otlp, otlphttp]

  2. and I have a exporter running at port 4318 on localhost and OTEL setup is deployed using docker-compose using below docker compose file
  4. ## Docker Compose

version: "2"
services:

Jaeger

jaeger-all-in-one:
image: jaegertracing/all-in-one:latest
ports:
- "16686:16686"
- "14268"
- "14250:14250"

Zipkin

zipkin-all-in-one:
image: openzipkin/zipkin:latest
ports:
- "9411:9411"

Collector

otel-collector:
image: ${OTELCOL_IMG}
command: ["--config=/etc/otel-collector-config-demo.yaml", "${OTELCOL_ARGS}"]
volumes:
- ./otel-collector-config-demo.yaml:/etc/otel-collector-config-demo.yaml
ports:
- "1888:1888" # pprof extension
- "8888:8888" # Prometheus metrics exposed by the collector
- "8889:8889" # Prometheus exporter metrics
- "13133:13133" # health_check extension
- "55679:55679" # zpages extension
- "4317:4317" # otlp receiver
- "8000:8000" # parseable exporter
- "4318:4318"
depends_on:
- jaeger-all-in-one
- zipkin-all-in-one
environment:
OTEL_EXPORTER_OTLP_ENDPOINT: http://docker.for.mac.localhost:4318

prometheus:
container_name: prometheus
image: prom/prometheus:latest
volumes:
- ./prometheus.yaml:/etc/prometheus/prometheus.yml
ports:
- "9090:9090"

  2. ## On exporter side
  3. (written in Rust) I am seeing this error

[2023-06-01T22:29:27Z ERROR actix_http::h1::dispatcher] stream error: Request parse error: Invalid HTTP version specified
[2023-06-01T22:29:27Z ERROR actix_http::h1::dispatcher] stream error: Request parse error: Invalid HTTP version specified

  2. ## On OTEL Collector side
  3. I am seeing these errors

2023-06-01 23:29:27 }. Err: connection error: desc = "error reading server preface: http2: frame too large" {"grpc_log": true}
2023-06-01 23:29:27 2023-06-01T22:29:27.409Z warn zapgrpc/zapgrpc.go:195 [core] [Channel #5 SubChannel #6] grpc: addrConn.createTransport failed to connect to {
2023-06-01 23:29:27 "Addr": "docker.for.mac.localhost:4318",
2023-06-01 23:29:27 "ServerName": "docker.for.mac.localhost:4318",
2023-06-01 23:29:27 "Attributes": null,
2023-06-01 23:29:27 "BalancerAttributes": null,
2023-06-01 23:29:27 "Type": 0,
2023-06-01 23:29:27 "Metadata": null
2023-06-01 23:29:27 }. Err: connection error: desc = "error reading server preface: http2: frame too large" {"grpc_log": true}
2023-06-01 23:29:28 2023-06-01T22:29:28.405Z info jaegerexporter@v0.78.0/exporter.go:173 State of the connection with the Jaeger Collector backend {"kind": "exporter", "data_type": "traces", "name": "jaeger", "state": "READY"}

  2. I suspect OTLP Collector is making and HTTP/2 call which makes it fail.
  4. ## EDIT 1
  5. I tried removing otlphttp completely from configuration and still got same errors on both exporter and collector side.
  6. ### On Exporter

[2023-06-02T07:26:54Z ERROR actix_http::h1::dispatcher] stream error: Request parse error: Invalid HTTP version specified
[2023-06-02T07:26:54Z ERROR actix_http::h1::dispatcher] stream error: Request parse error: Invalid HTTP version specified

  2. ### On Collector

2023-06-02 08:26:54 docker-otel-collector-1 | 2023-06-02T07:26:54.482Z warn zapgrpc/zapgrpc.go:195 [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {
2023-06-02 08:26:54 docker-otel-collector-1 | "Addr": "docker.for.mac.localhost:4318",
2023-06-02 08:26:54 docker-otel-collector-1 | "ServerName": "docker.for.mac.localhost:4318",
2023-06-02 08:26:54 docker-otel-collector-1 | "Attributes": null,
2023-06-02 08:26:54 docker-otel-collector-1 | "BalancerAttributes": null,
2023-06-02 08:26:54 docker-otel-collector-1 | "Type": 0,
2023-06-02 08:26:54 docker-otel-collector-1 | "Metadata": null
2023-06-02 08:26:54 docker-otel-collector-1 | }. Err: connection error: desc = "error reading server preface: http2: frame too large" {"grpc_log": true}

  2. ## EDIT 2
  3. When I only configured otlphttp and removed otlp config section. Then there was no effect at all.
  4. Neither collector sent anything nor exporter received anything.
  5. My latest configuration looks like below

receivers:
otlp:
protocols:
grpc:
http:

exporters:
otlphttp:
endpoint: "http://docker.for.mac.localhost:4318"
tls:
insecure: true
headers:
Authorization: "Basic YWRtaW46YWRtaW4="
X-P-Stream: "demo"
X-P-TAG-tag1: "value1"
X-P-META-meta1: "value1"
Content-type: "application/json"
prometheus:
endpoint: "0.0.0.0:8889"
namespace: promexample
const_labels:
label1: value1
logging:
loglevel: debug

zipkin:
endpoint: "http://zipkin-all-in-one:9411/api/v2/spans"
format: proto

jaeger:
endpoint: jaeger-all-in-one:14250
tls:
insecure: true

Alternatively, use jaeger_thrift_http with the settings below. In this case

update the list of exporters on the traces pipeline.

jaeger_thrift_http:

url: http://jaeger-all-in-one:14268/api/traces

processors:
batch:

extensions:
health_check:
pprof:
endpoint: :1888
zpages:
endpoint: :55679

service:
extensions: [pprof, zpages, health_check]
pipelines:
traces:
receivers: [otlp]
processors: [batch]
exporters: [logging, zipkin, jaeger, otlphttp]
metrics:
receivers: [otlp]
processors: [batch]
exporters: [logging, prometheus, otlphttp]

  1. #### Collector Debug logs

2023-06-02T08:23:30.909Z info service/telemetry.go:104 Setting up own telemetry...
2023-06-02T08:23:30.909Z info service/telemetry.go:127 Serving Prometheus metrics {"address": ":8888", "level": "Basic"}
2023-06-02T08:23:30.909Z debug extension/extension.go:135 Beta component. May change in the future. {"kind": "extension", "name": "pprof"}
2023-06-02T08:23:30.909Z debug extension/extension.go:135 Beta component. May change in the future. {"kind": "extension", "name": "zpages"}
2023-06-02T08:23:30.909Z debug extension/extension.go:135 Beta component. May change in the future. {"kind": "extension", "name": "health_check"}
2023-06-02T08:23:30.909Z debug exporter@v0.78.2/exporter.go:273 Beta component. May change in the future. {"kind": "exporter", "data_type": "metrics", "name": "prometheus"}
2023-06-02T08:23:30.910Z debug exporter@v0.78.2/exporter.go:273 Stable component. {"kind": "exporter", "data_type": "metrics", "name": "otlphttp"}
2023-06-02T08:23:30.910Z info exporter@v0.78.2/exporter.go:275 Development component. May change in the future. {"kind": "exporter", "data_type": "traces", "name": "logging"}
2023-06-02T08:23:30.910Z warn loggingexporter@v0.78.2/factory.go:98 'loglevel' option is deprecated in favor of 'verbosity'. Set 'verbosity' to equivalent value to preserve behavior. {"kind": "exporter", "data_type": "traces", "name": "logging", "loglevel": "debug", "equivalent verbosity level": "Detailed"}
2023-06-02T08:23:30.910Z info exporter@v0.78.2/exporter.go:275 Development component. May change in the future. {"kind": "exporter", "data_type": "metrics", "name": "logging"}
2023-06-02T08:23:30.910Z debug processor/processor.go:287 Stable component. {"kind": "processor", "name": "batch", "pipeline": "metrics"}
2023-06-02T08:23:30.910Z debug exporter@v0.78.2/exporter.go:273 Beta component. May change in the future. {"kind": "exporter", "data_type": "traces", "name": "zipkin"}
2023-06-02T08:23:30.910Z info exporter@v0.78.2/exporter.go:275 Deprecated component. Will be removed in future releases. {"kind": "exporter", "data_type": "traces", "name": "jaeger"}
2023-06-02T08:23:30.910Z warn jaegerexporter@v0.78.0/factory.go:43 jaeger exporter is deprecated and will be removed in July 2023. See https://github.com/open-telemetry/opentelemetry-specification/pull/2858 for more details. {"kind": "exporter", "data_type": "traces", "name": "jaeger"}
2023-06-02T08:23:30.910Z debug exporter@v0.78.2/exporter.go:273 Stable component. {"kind": "exporter", "data_type": "traces", "name": "otlphttp"}
2023-06-02T08:23:30.910Z debug processor/processor.go:287 Stable component. {"kind": "processor", "name": "batch", "pipeline": "traces"}
2023-06-02T08:23:30.910Z debug receiver@v0.78.2/receiver.go:294 Stable component. {"kind": "receiver", "name": "otlp", "data_type": "traces"}
2023-06-02T08:23:30.910Z debug receiver@v0.78.2/receiver.go:294 Stable component. {"kind": "receiver", "name": "otlp", "data_type": "metrics"}
2023-06-02T08:23:30.911Z info service/service.go:131 Starting otelcol-contrib... {"Version": "0.78.0", "NumCPU": 4}
2023-06-02T08:23:30.911Z info extensions/extensions.go:30 Starting extensions...
2023-06-02T08:23:30.911Z info extensions/extensions.go:33 Extension is starting... {"kind": "extension", "name": "pprof"}
2023-06-02T08:23:30.911Z info pprofextension@v0.78.0/pprofextension.go:60 Starting net/http/pprof server {"kind": "extension", "name": "pprof", "config": {"TCPAddr":{"Endpoint":":1888"},"BlockProfileFraction":0,"MutexProfileFraction":0,"SaveToFile":""}}
2023-06-02T08:23:30.911Z info extensions/extensions.go:37 Extension started. {"kind": "extension", "name": "pprof"}
2023-06-02T08:23:30.911Z info extensions/extensions.go:33 Extension is starting... {"kind": "extension", "name": "zpages"}
2023-06-02T08:23:30.911Z info zpagesextension@v0.78.2/zpagesextension.go:53 Registered zPages span processor on tracer provider {"kind": "extension", "name": "zpages"}
2023-06-02T08:23:30.911Z info zpagesextension@v0.78.2/zpagesextension.go:63 Registered Host's zPages {"kind": "extension", "name": "zpages"}
2023-06-02T08:23:30.911Z info zpagesextension@v0.78.2/zpagesextension.go:75 Starting zPages extension {"kind": "extension", "name": "zpages", "config": {"TCPAddr":{"Endpoint":":55679"}}}
2023-06-02T08:23:30.911Z info extensions/extensions.go:37 Extension started. {"kind": "extension", "name": "zpages"}
2023-06-02T08:23:30.911Z info extensions/extensions.go:33 Extension is starting... {"kind": "extension", "name": "health_check"}
2023-06-02T08:23:30.911Z info healthcheckextension@v0.78.0/healthcheckextension.go:34 Starting health_check extension {"kind": "extension", "name": "health_check", "config": {"Endpoint":"0.0.0.0:13133","TLSSetting":null,"CORS":null,"Auth":null,"MaxRequestBodySize":0,"IncludeMetadata":false,"Path":"/","ResponseBody":null,"CheckCollectorPipeline":{"Enabled":false,"Interval":"5m","ExporterFailureThreshold":5}}}
2023-06-02T08:23:30.911Z warn internal/warning.go:40 Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks {"kind": "extension", "name": "health_check", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2023-06-02T08:23:30.911Z info extensions/extensions.go:37 Extension started. {"kind": "extension", "name": "health_check"}
2023-06-02T08:23:30.911Z warn internal/warning.go:40 Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks {"kind": "exporter", "data_type": "metrics", "name": "prometheus", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2023-06-02T08:23:30.911Z warn internal/warning.go:40 Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks {"kind": "receiver", "name": "otlp", "data_type": "traces", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2023-06-02T08:23:30.911Z info zapgrpc/zapgrpc.go:178 [core] [Server #1] Server created {"grpc_log": true}
2023-06-02T08:23:30.911Z info otlpreceiver@v0.78.2/otlp.go:83 Starting GRPC server {"kind": "receiver", "name": "otlp", "data_type": "traces", "endpoint": "0.0.0.0:4317"}
2023-06-02T08:23:30.912Z warn internal/warning.go:40 Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks {"kind": "receiver", "name": "otlp", "data_type": "traces", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2023-06-02T08:23:30.912Z info otlpreceiver@v0.78.2/otlp.go:101 Starting HTTP server {"kind": "receiver", "name": "otlp", "data_type": "traces", "endpoint": "0.0.0.0:4318"}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Server #1 ListenSocket #2] ListenSocket created {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] Channel created {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] original dial target is: "jaeger-all-in-one:14250" {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] parsed dial target is: {Scheme:jaeger-all-in-one Authority: URL:{Scheme:jaeger-all-in-one Opaque:14250 User: Host: Path: RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] fallback to scheme "passthrough" {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] parsed dial target is: {Scheme:passthrough Authority: URL:{Scheme:passthrough Opaque: User: Host: Path:/jaeger-all-in-one:14250 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}} {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] Channel authority set to "jaeger-all-in-one:14250" {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] Resolver state updated: {
"Addresses": [
{
"Addr": "jaeger-all-in-one:14250",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses) {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] Channel switches to new LB policy "pick_first" {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3 SubChannel #4] Subchannel created {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] Channel Connectivity change to CONNECTING {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to CONNECTING {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3 SubChannel #4] Subchannel picks a new address "jaeger-all-in-one:14250" to connect {"grpc_log": true}
2023-06-02T08:23:30.912Z info zapgrpc/zapgrpc.go:178 [core] pickfirstBalancer: UpdateSubConnState: 0x4000cda078, {CONNECTING <nil>} {"grpc_log": true}
2023-06-02T08:23:30.913Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3 SubChannel #4] Subchannel Connectivity change to READY {"grpc_log": true}
2023-06-02T08:23:30.914Z info zapgrpc/zapgrpc.go:178 [core] pickfirstBalancer: UpdateSubConnState: 0x4000cda078, {READY <nil>} {"grpc_log": true}
2023-06-02T08:23:30.914Z info zapgrpc/zapgrpc.go:178 [core] [Channel #3] Channel Connectivity change to READY {"grpc_log": true}
2023-06-02T08:23:30.914Z info jaegerexporter@v0.78.0/exporter.go:173 State of the connection with the Jaeger Collector backend {"kind": "exporter", "data_type": "traces", "name": "jaeger", "state": "READY"}
2023-06-02T08:23:30.914Z info healthcheck/handler.go:129 Health Check state change {"kind": "extension", "name": "health_check", "status": "ready"}
2023-06-02T08:23:30.914Z info service/service.go:148 Everything is ready. Begin running and processing data.
2023-06-02T08:23:35.806Z debug prometheusexporter@v0.78.0/collector.go:360 collect called {"kind": "exporter", "data_type": "metrics", "name": "prometheus"}
2023-06-02T08:23:35.806Z debug prometheusexporter@v0.78.0/accumulator.go:268 Accumulator collect called {"kind": "exporter", "data_type": "metrics", "name": "prometheus"}

  2. I can only see `prometheus exporter` being called in debug calls and otlphttp exporter is not called at all.
  4. ## Edit 3
  5. Configuration using port 4317

receivers:
otlp:
protocols:
grpc:
http:

exporters:
otlphttp:
endpoint: "http://docker.for.mac.localhost:4317"
tls:
insecure: true
headers:
Authorization: "Basic YWRtaW46YWRtaW4="
X-P-Stream: "demo"
X-P-TAG-tag1: "value1"
X-P-META-meta1: "value1"
Content-type: "application/json"
prometheus:
endpoint: "0.0.0.0:8889"
namespace: promexample
const_labels:
label1: value1
logging:
loglevel: debug

zipkin:
endpoint: "http://zipkin-all-in-one:9411/api/v2/spans"
format: proto

jaeger:
endpoint: jaeger-all-in-one:14250
tls:
insecure: true

Alternatively, use jaeger_thrift_http with the settings below. In this case

update the list of exporters on the traces pipeline.

jaeger_thrift_http:

url: http://jaeger-all-in-one:14268/api/traces

processors:
batch:

extensions:
health_check:
pprof:
endpoint: :1888
zpages:
endpoint: :55679

service:
telemetry:
logs:
level: "debug"
extensions: [pprof, zpages, health_check]
pipelines:
traces:
receivers: [otlp]
processors: [batch]
exporters: [logging, zipkin, jaeger, otlphttp]
metrics:
receivers: [otlp]
processors: [batch]
exporters: [logging, prometheus, otlphttp]

  2. Just for reference my exporter has following endpoints exposed..

http://localhost:4318/v1/metrics
http://localhost:4318/v1/logs
http://localhost:4318/v1/traces

  4. </details>
  7. # 答案1
  8. **得分**: 1
  10. 你已经配置了两个导出器（gRPC 和 HTTP）来使用相同的端口：
  12. ```yaml
  13. otlp:
  14.     endpoint: "http://docker.for.mac.localhost:4318"
  15. ...
  16.   otlphttp:
  17.     endpoint: "http://docker.for.mac.localhost:4318"

当你向 gRPC 端点发送 HTTP 请求时，它会失败。移除 otlphttp 导出器或在端口 4317 上设置 otlphttp 接收器。

你的配置将如下所示：

  1. receivers:
  2.   otlp:
  3.     protocols:
  4.         grpc:
  5.         http:
  7. exporters:
  8.   otlp:
  9.     endpoint: "http://docker.for.mac.localhost:4318"
  10.     tls:
  11.       insecure: true
  12.     headers: 
  13.       Authorization: "Basic YWRtaW46YWRtaW4="
  14.       X-P-Stream: "demo"
  15.       X-P-TAG-tag1: "value1"
  16.       X-P-META-meta1: "value1"
  17.       Content-type: "application/json"
  18.   otlphttp:
  19.     endpoint: "http://docker.for.mac.localhost:4317"
  20.     tls:
  21.       insecure: true
  22.     headers: 
  23.       Authorization: "Basic YWRtaW46YWRtaW4="
  24.       X-P-Stream: "demo"
  25.       X-P-TAG-tag1: "value1"
  26.       X-P-META-meta1: "value1"
  27.       Content-type: "application/json"
  28.   prometheus:
  29.     endpoint: "0.0.0.0:8889"
  30.     namespace: promexample
  31.     const_labels:
  32.       label1: value1
  33.   logging:
  34.     loglevel: debug
  36.   zipkin:
  37.     endpoint: "http://zipkin-all-in-one:9411/api/v2/spans"
  38.     format: proto
  40.   jaeger:
  41.     endpoint: jaeger-all-in-one:14250
  42.     tls:
  43.       insecure: true
  45. # 或者，使用以下设置使用 jaeger_thrift_http。在这种情况下，
  46. # 更新跟踪管道上的导出器列表。
  47. #
  48. #  jaeger_thrift_http:
  49. #    url: http://jaeger-all-in-one:14268/api/traces
  51. processors:
  52.   batch:
  54. extensions:
  55.   health_check:
  56.   pprof:
  57.     endpoint: :1888
  58.   zpages:
  59.     endpoint: :55679
  61. service:
  62.   extensions: [pprof, zpages, health_check]
  63.   pipelines:
  64.     traces:
  65.       receivers: [otlp]
  66.       processors: [batch]
  67.       exporters: [logging, zipkin, jaeger, otlp, otlphttp]
  68.     metrics:
  69.       receivers: [otlp]
  70.       processors: [batch]
  71.       exporters: [logging, prometheus, otlp, otlphttp]

请确保在 docker-compose.yml 中暴露 4317 端口。

请尝试并告诉我们是否有效。

英文:

You have configured both exporters (gRPC and HTTP) to use the same port:

  1. otlp:
  2. endpoint: &quot;http://docker.for.mac.localhost:4318&quot;
  3. ...
  4. otlphttp:
  5. endpoint: &quot;http://docker.for.mac.localhost:4318&quot;

When you send a HTTP request to the gRPC endpoint, it fails. Remove the otlphttp exporter or set up the otlphttp receiver on port 4317.

Your configuration would then look like:

  1. receivers:
  2. otlp:
  3. protocols:
  4. grpc:
  5. http:
  6. exporters:
  7. otlp:
  8. endpoint: &quot;http://docker.for.mac.localhost:4318&quot;
  9. tls:
  10. insecure: true
  11. headers: 
  12. Authorization: &quot;Basic YWRtaW46YWRtaW4=&quot;
  13. X-P-Stream: &quot;demo&quot;
  14. X-P-TAG-tag1: &quot;value1&quot;
  15. X-P-META-meta1: &quot;value1&quot;
  16. Content-type: &quot;application/json&quot;
  17. otlphttp:
  18. endpoint: &quot;http://docker.for.mac.localhost:4317&quot;
  19. tls:
  20. insecure: true
  21. headers: 
  22. Authorization: &quot;Basic YWRtaW46YWRtaW4=&quot;
  23. X-P-Stream: &quot;demo&quot;
  24. X-P-TAG-tag1: &quot;value1&quot;
  25. X-P-META-meta1: &quot;value1&quot;
  26. Content-type: &quot;application/json&quot;
  27. prometheus:
  28. endpoint: &quot;0.0.0.0:8889&quot;
  29. namespace: promexample
  30. const_labels:
  31. label1: value1
  32. logging:
  33. loglevel: debug
  34. zipkin:
  35. endpoint: &quot;http://zipkin-all-in-one:9411/api/v2/spans&quot;
  36. format: proto
  37. jaeger:
  38. endpoint: jaeger-all-in-one:14250
  39. tls:
  40. insecure: true
  41. # Alternatively, use jaeger_thrift_http with the settings below. In this case
  42. # update the list of exporters on the traces pipeline.
  43. #
  44. #  jaeger_thrift_http:
  45. #    url: http://jaeger-all-in-one:14268/api/traces
  46. processors:
  47. batch:
  48. extensions:
  49. health_check:
  50. pprof:
  51. endpoint: :1888
  52. zpages:
  53. endpoint: :55679
  54. service:
  55. extensions: [pprof, zpages, health_check]
  56. pipelines:
  57. traces:
  58. receivers: [otlp]
  59. processors: [batch]
  60. exporters: [logging, zipkin, jaeger, otlp, otlphttp]
  61. metrics:
  62. receivers: [otlp]
  63. processors: [batch]
  64. exporters: [logging, prometheus, otlp, otlphttp]

Make sure to expose 4317 in docker-compose.yml as well.

Please try it out and let us know if it worked.

huangapple
  • 本文由 发表于 2023年6月2日 06:40:39
  • 转载请务必保留本文链接：https://go.coder-hub.com/76386139.html
  • docker
  • jaeger
  • open-telemetry
  • open-telemetry-collector
  • zipkin
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定