Hector Hernandez

Rename @opentelemetry/sdk-metrics-base to @opentelemetry/sdk-metrics

2

## Which problem is this PR solving? Renaming @opentelemetry/sdk-metrics-base package to @opentelemetry/sdk-metrics Fixes #3137 ## Type of change - [ ] Breaking change (fix or feature that would cause existing...

Add HTTP Server and Client duration Metrics in HTTP Node.js Instrumentation

1

## Which problem is this PR solving? Add HTTP Server and Client duration Metrics in HTTP Node.js Instrumentation. Fixes #3148 ## Short description of the changes Adding support for duration...

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/semantic_conventions/http-metrics.md

Added duration metrics for server/client in internal MetricsInstrumentation Exceptions and traces standard metrics continue to work as before Added SpanProcessor to add extra properties in spans

Automatic tracking of incoming requests not enabled when createServer is not called

2

Current code rely on createServer to be called to start generatign the telemetry, we need to support other use cases like the following ` const express = require('express'); const http...

[Azure Monitor Exporter] Export Metric attributes

1

Added metric attributes Create an envelope per metric data point

PushMetricExporter forceFlush behavior

4

I'm building a Metrics Exporter for Azure Monitor and noticed some weird behavior in [PushMetricExporter](https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/packages/opentelemetry-sdk-metrics-base/src/export/MetricExporter.ts#L28) interface, this one is exposing forceFlush, I would expect the MetricReader to be the one...

[sdk-node] allow multiple spanProcessors/logProcessors to be configured

4

spanProcessors and logProcessors order is important when they are doing some modification of the actual span/log, allowing multiple ones will permit more specific scenarios.