Using @otel/sdk-metrics-base with @otel/exporter-metrics-otlp-http

[michaelfig]

I'm trying to use under Node.js:

import {
  MeterProvider,
  ConsoleMetricExporter,
} from '@opentelemetry/sdk-metrics-base';
import { OTLPMetricExporter } from '@opentelemetry/exporter-metrics-otlp-http';
import { PrometheusExporter } from '@opentelemetry/exporter-prometheus';

  const exporter = new OTLPMetricExporter();
  console.info('Enabling OTLP Metrics Exporter to', exporter.getDefaultUrl({}));

  return new MeterProvider({
    exporter,
    interval: 1000,
  });

with my environment, I get:

Enabling OTLP Metrics Exporter to http://127.0.0.1:4317/v1/metrics

but when (for debugging) I first listen on port 4317, nothing ever connects to it. Here are my module versions:

$ rg '^"@opentel' ../../yarn.lock 
3866:"@opentelemetry/api-metrics@0.27.0":
3871:"@opentelemetry/api@>=1.0.0 <1.1.0":
3876:"@opentelemetry/core@1.0.1":
3883:"@opentelemetry/exporter-metrics-otlp-http@^0.27.0":
3894:"@opentelemetry/exporter-prometheus@^0.27.0":
3903:"@opentelemetry/exporter-trace-otlp-http@0.27.0", "@opentelemetry/exporter-trace-otlp-http@^0.27.0":
3912:"@opentelemetry/resources@1.0.1":
3920:"@opentelemetry/sdk-metrics-base@0.27.0", "@opentelemetry/sdk-metrics-base@^0.27.0":
3930:"@opentelemetry/sdk-trace-base@1.0.1", "@opentelemetry/sdk-trace-base@^1.0.1":
3939:"@opentelemetry/semantic-conventions@1.0.1":
$

Using the Prometheus exporter, the metrics are made available for scraping correctly.

[michaelfig]

I found a similar no-network-connection behaviour when attempting to use @otel/exporter-trace-otlp-http. I must be missing something.

[michaelfig]

I'm silly, the otel initialisation code wasn't enabled from within my app. Forgive the noise.