Skip to content
New issue

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

Error: PeriodicExportingMetricReader: metrics export failed #976

Closed
CatsMiaow opened this issue Nov 19, 2024 · 1 comment
Closed

Error: PeriodicExportingMetricReader: metrics export failed #976

CatsMiaow opened this issue Nov 19, 2024 · 1 comment

Comments

@CatsMiaow
Copy link

  • @splunk/otel v2.14.0
  • Node.js v20.18.0
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

"@opentelemetry/sdk-metrics": "1.26.0",

The bug with PeriodicExportingMetricReader seems to be fixed in v1.27.0, v1.28.0.

@seemk
Copy link
Contributor

seemk commented Dec 5, 2024

Thanks, I've released 2.15.0 which is using sdk-metrics 1.28.0. Hopefully it resolves the issue, please reopen if you still see it.

@seemk seemk closed this as completed Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants