OpenTelemetry exporter fails with message Cannot read property 'Resolver' of undefined #281
Comments
jussisjostrom
added
bug
|
Hi @jussisjostrom, New versions of OTEL library can't be used because node.js is too old and OTEL libs has been updated and it fails now. So it even fails on the version that worked in the past: the server side was updated and as result the client side (TS) tries to trigger the code that even does not exist in the library or does not work on node.js 8.11.1 |
|
you can try http/protobuf instead of grpc if you server configured to accept it |
|
Same problem here after upgrading to Telemetry 1.37 "f5-collector": { What's the plan? should we revert back to previous version or will someone fix issue? |
|
Telemetry 1.36 has the same issue. |
|
Hi @PatricDahl New versions of OTEL library can't be used because node.js is too old and OTEL libs has been updated and it fails now. So it even fails on the version that worked in the past: the server side was updated and as result the client side (TS) tries to trigger the code that even does not exist in the library or does not work on node.js 8.11.1. Can you try http/protobuf instead of grpc if you server configured to accept it? |
Environment
Summary
Opentelemetry_Exporter type of consumer fails to send the collected metrics.
Verifying by tcpdump on the target shows that no attempt to open the tcp connection to send the report is made.
In the /var/log/restnoded/restnoded.log file this line is printed:
Impact is that I cannot use gRPC to send Opentelemetry reports from BIG-IP.
Steps To Reproduce
Steps to reproduce the behavior:
{ "$schema": "https://raw.githubusercontent.com/F5Networks/f5-telemetry-streaming/master/src/schema/latest/base_schema.json", "class": "Telemetry", "schemaVersion": "1.36.0", "controls": { "class": "Controls", "logLevel": "debug", "debug": false, "memoryMonitor": { "logFrequency": 60 }, "memoryThresholdPercent": 90 }, "Listener": { "class": "Telemetry_Listener", "port": 6514, "enable": true, "trace": false, "match": "", "actions": [ { "setTag": { "tenant": "`T`", "application": "`A`" }, "enable": true } ] }, "defaultPoller": { "class": "Telemetry_System_Poller", "interval": 60, "host": "localhost", "port": 8100, "protocol": "http", "allowSelfSignedCert": true, "enable": true, "workers": 5, "chunkSize": 30 }, "telemetrySystem": { "class": "Telemetry_System", "enable": true, "systemPoller": [ "defaultPoller" ], "host": "localhost", "port": 8100, "protocol": "http", "enableHostConnectivityCheck": false, "allowSelfSignedCert": true }, "SRV01_OTEL_GRPC_NOSSL": { "class": "Telemetry_Consumer", "type": "OpenTelemetry_Exporter", "enable": true, "trace": true, "host": "IP-address-redacted", "port": 4317, "exporter": "grpc", "convertBooleansToMetrics": false, "useSSL": false } }{ "message": "success", "declaration": { ...Expected Behavior
The consumer of type OpenTelemetry_Exporter would be succesful in sending telemetry reports using gRPC.
Actual Behavior
No report is sent out. Based on logs, data is collected, but sending to the consumer fails even before a TCP connection is attempted:
The text was updated successfully, but these errors were encountered: