We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
import { start } from '@splunk/otel'; start({ serviceName: process.env.xxx, endpoint: process.env.xxx, metrics: { endpoint: process.env.xxx, runtimeMetricsEnabled: true, }, profiling: { memoryProfilingEnabled: true, }, tracing: true, });
/app/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:76 throw new Error(`PeriodicExportingMetricReader: metrics export failed (error ${result.error})`); ^ Error: PeriodicExportingMetricReader: metrics export failed (error Error: 13 INTERNAL: Received RST_STREAM with code 2 triggered by internal client error: Protocol error) at doExport (/app/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:76:23) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
When you start the application, an error occurs and the app crashes.
@splunk/otel v2.14.0 is using @opentelemetry/sdk-metrics v1.26.0
@splunk/otel
@opentelemetry/sdk-metrics
splunk-otel-js/package.json
Line 153 in c89f1a9
The bug with PeriodicExportingMetricReader seems to be fixed in v1.27.0, v1.28.0.
PeriodicExportingMetricReader
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When you start the application, an error occurs and the app crashes.
@splunk/otel
v2.14.0 is using@opentelemetry/sdk-metrics
v1.26.0splunk-otel-js/package.json
Line 153 in c89f1a9
The bug with
PeriodicExportingMetricReader
seems to be fixed in v1.27.0, v1.28.0.The text was updated successfully, but these errors were encountered: