v15.6.0
@promster/apollo@15.6.0
Minor Changes
-
#1581
27773f8Thanks @tdeekens! - AddcreateHistogram,createCounter,createGaugeandcreateSummaryhelpers 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
-
#1583
773bc5cThanks @tdeekens! - chore(deps): update dependencies from dependency dashboard -
Updated dependencies [
27773f8,27773f8,27fe810,773bc5c]:- @promster/metrics@15.6.0
@promster/express@15.6.0
Minor Changes
-
#1581
27773f8Thanks @tdeekens! - AddcreateHistogram,createCounter,createGaugeandcreateSummaryhelpers 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
-
#1583
773bc5cThanks @tdeekens! - chore(deps): update dependencies from dependency dashboard -
Updated dependencies [
27773f8,27773f8,27fe810,773bc5c]:- @promster/metrics@15.6.0
@promster/fastify@15.6.0
Minor Changes
-
#1581
27773f8Thanks @tdeekens! - AddcreateHistogram,createCounter,createGaugeandcreateSummaryhelpers 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
-
#1583
773bc5cThanks @tdeekens! - chore(deps): update dependencies from dependency dashboard -
Updated dependencies [
27773f8,27773f8,27fe810,773bc5c]:- @promster/metrics@15.6.0
- @promster/server@15.6.0
@promster/hapi@15.6.0
Minor Changes
-
#1581
27773f8Thanks @tdeekens! - AddcreateHistogram,createCounter,createGaugeandcreateSummaryhelpers 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
-
#1583
773bc5cThanks @tdeekens! - chore(deps): update dependencies from dependency dashboard -
Updated dependencies [
27773f8,27773f8,27fe810,773bc5c]:- @promster/metrics@15.6.0
@promster/marblejs@15.6.0
Minor Changes
-
#1581
27773f8Thanks @tdeekens! - AddcreateHistogram,createCounter,createGaugeandcreateSummaryhelpers 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
-
#1583
773bc5cThanks @tdeekens! - chore(deps): update dependencies from dependency dashboard -
Updated dependencies [
27773f8,27773f8,27fe810,773bc5c]:- @promster/metrics@15.6.0
@promster/metrics@15.6.0
Minor Changes
-
#1581
27773f8Thanks @tdeekens! - AddcreateHistogram,createCounter,createGaugeandcreateSummaryhelpers 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
-
#1583
773bc5cThanks @tdeekens! - chore(deps): update dependencies from dependency dashboard -
Updated dependencies [
27773f8,27773f8,27fe810,773bc5c]:- @promster/metrics@15.6.0