Skip to content

Latest commit

 

History

History
377 lines (223 loc) · 20.5 KB

CHANGELOG.md

File metadata and controls

377 lines (223 loc) · 20.5 KB

@promster/server

14.0.0

Patch Changes

13.0.0

Major Changes

  • #1175 2da8d99 Thanks @tdeekens! - Remove support for Node.js v18

    We didn't adjust functionality to remove support but changed the engines requirement.

Patch Changes

12.1.0

Minor Changes

Patch Changes

12.0.0

Major Changes

Minor Changes

Patch Changes

9.0.0

Major Changes

  • #1099 c3fbd90 Thanks @tdeekens! - Allow customization of individual metrics.

    Previously we only allowed customizing a all histogram and percentile based metrics once with a buckets and percentiles option. This is too restrictive in cases in which you need to customize metrics individually.

    As a result you can now pass metricBuckets and metricPercentiles as options. Both of which are a Record<string, number[]>. The key needs to match a an existing metric type.

    This is a more elaborate example:

    const middleware = createMiddleware({
  app,
  options: {
    metricBuckets: {
      httpRequestContentLengthInBytes: [
        100000, 200000, 500000, 1000000, 1500000, 2000000, 3000000, 5000000,
        10000000,
      ],
      httpRequestDurationInSeconds: [
        0.05, 0.1, 0.3, 0.5, 0.8, 1, 1.5, 2, 3, 10,
      ],
    },
    metricPercentiles: {
      httpRequestDurationPerPercentileInSeconds: [0.5, 0.9, 0.95, 0.98, 0.99],
      httpResponseContentLengthInBytes: [
        100000, 200000, 500000, 1000000, 1500000, 2000000, 3000000, 5000000,
        10000000,
      ],
    },
  },
});

    If you used buckets or percentiles before you migrate the values into the structure above.

Patch Changes

8.0.0

Major Changes

  • #1088 7cfd21c Thanks @tdeekens! - Breaking droping support for Node.js v14

  • #1087 2e848c1 Thanks @roumigus! - The up metric of each server integrating @promster has been renamed to nodejs_up. This is to avoid a collision with the existing up metric Prometheus uses.

    You can still rename this metric to anything you prefer when condfigurating @promster/express for instance like this:

    const prometheusMetricsMiddleware = createPrometheusMetricsMiddleware({
  options: {
    metricNames: {
      up: ["service_name_up"],
    },
  },
});

Patch Changes

7.0.8

Patch Changes

7.0.7

Patch Changes

7.0.6

Patch Changes

7.0.5

Patch Changes

7.0.4

Patch Changes

7.0.3

Patch Changes

7.0.2

Patch Changes

7.0.1

Patch Changes

  • #785 c619be8 Thanks @tdeekens! - Refactor all tests to integration tests setting up two servers. One for metric exposure and the other to trigger metrics.

7.0.0

Major Changes

  • #758 f02e6fe Thanks @tdeekens! - We droped support for Node.js < 14 via the engines field of the respective package.json files.

    We didn't make any changes to our code to prevent e.g. Node.js v9 to work but will not claim to officially support it any longer.

Patch Changes

6.0.6

Patch Changes

6.0.5

Patch Changes

6.0.4

Patch Changes

6.0.3

Patch Changes

  • #703 e351e91 Thanks @tdeekens! - Refactor to require Node.js v14 and drop official support for anything below

    The engines field of the package.json now requires Node.js v14 and not v9 as prior. There are no actual changes in the library however anything smaler v14 will not be officially supported.

  • Updated dependencies [e351e91, e2a1595, e351e91]:

6.0.2

Patch Changes

6.0.1

Patch Changes

6.0.0

Major Changes

  • daf8605 #557 Thanks @tdeekens! - # Breaking Changes

    This requires your to update your peer dependency of prom-client to v13.

    The new version of prom-client has additional small breaking changes promster has to incorporate which can leak into your application.

    If you do not use our @promster/server package and have a res.send(register.metrics()) you have to change it to res.send(await register.metrics()).

    You can find more on the prom-client changes here.

Patch Changes

5.0.0

Major Changes

  • 0eb64ca #529 Thanks @tdeekens! - # Introduction

    refactor: to use preconstruct for building

    Prior TypeScript was used to build bundles. In all this should not affect consumers of this library. Under the hood preconstruct uses rollup and babel which is now instructed to build for Node.js v12 using the preset-env preset.

    Breaking Change

    This release can potentially be breaking for you. We want to respect semantic versioning and follow it strictly.

    While migrating to preconstruct the version exports had to be removed as preconstruct's rollup will not resolve them. If you relied on this value you should either load the package.json of each module yourself or drop the usage.

    - const { version } = require('@promster/server');
+ const { version } = require('@promster/server/package.json');

Patch Changes

4.2.16

Patch Changes

4.2.15

Patch Changes

4.2.14

Patch Changes

4.2.13

Patch Changes

4.2.12

Patch Changes