Skip to content

v15.6.0

Choose a tag to compare

@tdeekens tdeekens released this 14 Jul 14:36
· 34 commits to main since this release
b646252

@promster/apollo@15.6.0

Minor Changes

  • #1581 27773f8 Thanks @tdeekens! - Add createHistogram, createCounter, createGauge and createSummary helpers for registering custom metrics idempotently.

    All metrics share prom-client's global registry, so registering a metric whose name already exists throws (A metric with the name <name> has already been registered.). This happens when a metric-defining module is evaluated more than once, for example when a bundler or package manager ships duplicate physical copies of a package. The new helpers return the already registered metric instead of re-creating it. promster's own built-in HTTP, GraphQL and GC metrics now use these helpers too, so they no longer crash under the same conditions.

Patch Changes

@promster/express@15.6.0

Minor Changes

  • #1581 27773f8 Thanks @tdeekens! - Add createHistogram, createCounter, createGauge and createSummary helpers for registering custom metrics idempotently.

    All metrics share prom-client's global registry, so registering a metric whose name already exists throws (A metric with the name <name> has already been registered.). This happens when a metric-defining module is evaluated more than once, for example when a bundler or package manager ships duplicate physical copies of a package. The new helpers return the already registered metric instead of re-creating it. promster's own built-in HTTP, GraphQL and GC metrics now use these helpers too, so they no longer crash under the same conditions.

Patch Changes

@promster/fastify@15.6.0

Minor Changes

  • #1581 27773f8 Thanks @tdeekens! - Add createHistogram, createCounter, createGauge and createSummary helpers for registering custom metrics idempotently.

    All metrics share prom-client's global registry, so registering a metric whose name already exists throws (A metric with the name <name> has already been registered.). This happens when a metric-defining module is evaluated more than once, for example when a bundler or package manager ships duplicate physical copies of a package. The new helpers return the already registered metric instead of re-creating it. promster's own built-in HTTP, GraphQL and GC metrics now use these helpers too, so they no longer crash under the same conditions.

Patch Changes

@promster/hapi@15.6.0

Minor Changes

  • #1581 27773f8 Thanks @tdeekens! - Add createHistogram, createCounter, createGauge and createSummary helpers for registering custom metrics idempotently.

    All metrics share prom-client's global registry, so registering a metric whose name already exists throws (A metric with the name <name> has already been registered.). This happens when a metric-defining module is evaluated more than once, for example when a bundler or package manager ships duplicate physical copies of a package. The new helpers return the already registered metric instead of re-creating it. promster's own built-in HTTP, GraphQL and GC metrics now use these helpers too, so they no longer crash under the same conditions.

Patch Changes

@promster/marblejs@15.6.0

Minor Changes

  • #1581 27773f8 Thanks @tdeekens! - Add createHistogram, createCounter, createGauge and createSummary helpers for registering custom metrics idempotently.

    All metrics share prom-client's global registry, so registering a metric whose name already exists throws (A metric with the name <name> has already been registered.). This happens when a metric-defining module is evaluated more than once, for example when a bundler or package manager ships duplicate physical copies of a package. The new helpers return the already registered metric instead of re-creating it. promster's own built-in HTTP, GraphQL and GC metrics now use these helpers too, so they no longer crash under the same conditions.

Patch Changes

@promster/metrics@15.6.0

Minor Changes

  • #1581 27773f8 Thanks @tdeekens! - Add createHistogram, createCounter, createGauge and createSummary helpers for registering custom metrics idempotently.

    All metrics share prom-client's global registry, so registering a metric whose name already exists throws (A metric with the name <name> has already been registered.). This happens when a metric-defining module is evaluated more than once, for example when a bundler or package manager ships duplicate physical copies of a package. The new helpers return the already registered metric instead of re-creating it. promster's own built-in HTTP, GraphQL and GC metrics now use these helpers too, so they no longer crash under the same conditions.

Patch Changes

@promster/server@15.6.0

Patch Changes

@promster/types@15.6.0

Patch Changes

@promster/undici@15.6.0

Patch Changes