Skip to content

[all] migrate from deprecated addMetricReader to MeterProvider constructor option #2646

@pichlermarc

Description

@pichlermarc

Description

MeterProvider#addMetricReader() is deprecated in favor of a constructor option and will be removed in SDK 2.0. To ensure a smoother transition for the contrib repo when we publish SDK 2.0, we should take care of this before we release 2.0 on February 17.

This issue is considered done when we have applied these changes in all packages of this repository

  • we moved from MeterProvider#addMetricReader() to the constructor option
  • we made the necessary changes to the documentation

Packages checklist:

Note

For traigers/approvers/maintainers please link the appropriate PRs and update check boxes as we work through them. Some of these packages may not use this method anywhere. In that case, please simple mark them as done and add a comment "not used" by editing this issue.

  • @opentelemetry/resource-detector-alibaba-cloud
  • @opentelemetry/instrumentation-user-interaction
  • @opentelemetry/resource-detector-container
  • @opentelemetry/instrumentation-generic-pool
  • @opentelemetry/instrumentation-document-load
  • @opentelemetry/resource-detector-instana
  • @opentelemetry/instrumentation-nestjs-core
  • @opentelemetry/resource-detector-github
  • @opentelemetry/instrumentation-aws-lambda
  • @opentelemetry/resource-detector-azure
  • @opentelemetry/instrumentation-cassandra-driver
  • @opentelemetry/instrumentation-memcached
  • @opentelemetry/instrumentation-long-task
  • @opentelemetry/resource-detector-aws
  • @opentelemetry/resource-detector-gcp
  • @opentelemetry/instrumentation-aws-sdk
  • @opentelemetry/instrumentation-connect
  • @opentelemetry/instrumentation-express
  • @opentelemetry/instrumentation-fastify
  • @opentelemetry/instrumentation-graphql
  • @opentelemetry/instrumentation-ioredis
  • @opentelemetry/instrumentation-mongodb
  • @opentelemetry/instrumentation-redis-4
  • @opentelemetry/instrumentation-restify
  • @opentelemetry/instrumentation-winston
  • @opentelemetry/instrumentation-bunyan
  • @opentelemetry/instrumentation-mysql2
  • @opentelemetry/instrumentation-router
  • @opentelemetry/instrumentation-mysql
  • @opentelemetry/instrumentation-redis
  • @opentelemetry/instrumentation-hapi
  • @opentelemetry/instrumentation-knex
  • @opentelemetry/instrumentation-pino
  • @opentelemetry/instrumentation-dns
  • @opentelemetry/instrumentation-koa
  • @opentelemetry/instrumentation-net
  • @opentelemetry/propagator-ot-trace
  • @opentelemetry/instrumentation-pg
  • @opentelemetry/id-generator-aws-xray
  • @opentelemetry/propagator-instana
  • @opentelemetry/auto-configuration-propagators
  • @opentelemetry/plugin-react-load
  • @opentelemetry/instrumentation-lru-memoizer
  • @opentelemetry/instrumentation-runtime-node
  • @opentelemetry/propagation-utils
  • @opentelemetry/auto-instrumentations-node
  • @opentelemetry/instrumentation-dataloader
  • @opentelemetry/auto-instrumentations-web
  • @opentelemetry/propagator-aws-xray-lambda
  • @opentelemetry/instrumentation-socket.io
  • @opentelemetry/instrumentation-cucumber
  • @opentelemetry/instrumentation-mongoose
  • @opentelemetry/instrumentation-amqplib
  • @opentelemetry/instrumentation-kafkajs
  • @opentelemetry/instrumentation-tedious
  • @opentelemetry/host-metrics
  • @opentelemetry/redis-common
  • @opentelemetry/instrumentation-undici
  • @opentelemetry/sql-common
  • @opentelemetry/contrib-test-utils
  • @opentelemetry/baggage-span-processor
  • @opentelemetry/propagator-aws-xray
  • @opentelemetry/instrumentation-fs
  • @opentelemetry/winston-transport

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:feature-trackingA feature with sub-issues that need to be addressed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions