🔮 Add support for multiple metric names per metric

⭐️ Features

Add support for multiple metric names per metric

Assume within your infrastructure you want to migrate from metric_name to prefix_metric_name without loosing data or insight for moment.
With this release you can specify multiple names per metric type. This works for each type up, countOfGcs, durationOfGc, reclaimedInGc, httpRequestDurationPerPercentileInMilliseconds, httpRequestDurationInMilliseconds, httpRequestDurationPerPercentileInSeconds, httpRequestDurationInSeconds.
Each value can be an Array<String> so httpRequestDurationInMilliseconds: ['deprecated_name', 'next_name'].

During a transition period both names will be exposed to Prometheus:

Giving you time to migrate Recording Rules and any dashboard to eventually remove the deprecated name again.

🔮 Add support for multiple metric names per metric

⭐️ Features

Add support for multiple metric names per metric

Assume within your infrastructure you want to migrate from metric_name to prefix_metric_name without loosing data or insight for moment.
With this release you can specify multiple names per metric type. This works for each type up, countOfGcs, durationOfGc, reclaimedInGc, httpRequestDurationPerPercentileInMilliseconds, httpRequestDurationInMilliseconds, httpRequestDurationPerPercentileInSeconds, httpRequestDurationInSeconds.
Each value can be an Array<String> so httpRequestDurationInMilliseconds: ['deprecated_name', 'next_name'].

During a transition period both names will be exposed to Prometheus:

Giving you time to migrate Recording Rules and any dashboard to eventually remove the deprecated name again.

🔮 Add support for multiple metric names per metric

⭐️ Features

Add support for multiple metric names per metric

Assume within your infrastructure you want to migrate from metric_name to prefix_metric_name without loosing data or insight for moment.
With this release you can specify multiple names per metric type. This works for each type up, countOfGcs, durationOfGc, reclaimedInGc, httpRequestDurationPerPercentileInMilliseconds, httpRequestDurationInMilliseconds, httpRequestDurationPerPercentileInSeconds, httpRequestDurationInSeconds.
Each value can be an Array<String> so httpRequestDurationInMilliseconds: ['deprecated_name', 'next_name'].

During a transition period both names will be exposed to Prometheus:

Giving you time to migrate Recording Rules and any dashboard to eventually remove the deprecated name again.

🔮 Add support for multiple metric names per metric

⭐️ Features

Add support for multiple metric names per metric

Assume within your infrastructure you want to migrate from metric_name to prefix_metric_name without loosing data or insight for moment.
With this release you can specify multiple names per metric type. This works for each type up, countOfGcs, durationOfGc, reclaimedInGc, httpRequestDurationPerPercentileInMilliseconds, httpRequestDurationInMilliseconds, httpRequestDurationPerPercentileInSeconds, httpRequestDurationInSeconds.
Each value can be an Array<String> so httpRequestDurationInMilliseconds: ['deprecated_name', 'next_name'].

During a transition period both names will be exposed to Prometheus:

Giving you time to migrate Recording Rules and any dashboard to eventually remove the deprecated name again.

🔮 Add support for multiple metric names per metric

⭐️ Features

Add support for multiple metric names per metric

Assume within your infrastructure you want to migrate from metric_name to prefix_metric_name without loosing data or insight for moment.
With this release you can specify multiple names per metric type. This works for each type up, countOfGcs, durationOfGc, reclaimedInGc, httpRequestDurationPerPercentileInMilliseconds, httpRequestDurationInMilliseconds, httpRequestDurationPerPercentileInSeconds, httpRequestDurationInSeconds.
Each value can be an Array<String> so httpRequestDurationInMilliseconds: ['deprecated_name', 'next_name'].

During a transition period both names will be exposed to Prometheus:

Giving you time to migrate Recording Rules and any dashboard to eventually remove the deprecated name again.

🔮 Add support for multiple metric names per metric

⭐️ Features

Add support for multiple metric names per metric

Assume within your infrastructure you want to migrate from metric_name to prefix_metric_name without loosing data or insight for moment.
With this release you can specify multiple names per metric type. This works for each type up, countOfGcs, durationOfGc, reclaimedInGc, httpRequestDurationPerPercentileInMilliseconds, httpRequestDurationInMilliseconds, httpRequestDurationPerPercentileInSeconds, httpRequestDurationInSeconds.
Each value can be an Array<String> so httpRequestDurationInMilliseconds: ['deprecated_name', 'next_name'].

During a transition period both names will be exposed to Prometheus:

Giving you time to migrate Recording Rules and any dashboard to eventually remove the deprecated name again.

Adds `skip` option to omit a request from being recorded

🌟 Features

• Adds skip option to all packages to omit a request from being recorded.
  • The skip function receives req, res and labels and should return a boolean

{
   skip: (req, res, labels) => {
	  if (req.url.contains('foo') return true;
      if (labels.depreacted) return true;

      else return false;
   }
}

`prom-client` is now a peer dependency

💣 Breaking changes

• prom-client is now a peer dependency just add it to your dependencies with your package manager of choice

This solves issues with different libraries coming with their own prom-client leading to multiple default registries. This is unintended and can be solved by promster "just" assuming a prom-client being available.

`prom-client` is now a peer dependency

💣 Breaking changes

• prom-client is now a peer dependency just add it to your dependencies with your package manager of choice

This solves issues with different libraries coming with their own prom-client leading to multiple default registries. This is unintended and can be solved by promster "just" assuming a prom-client being available.

`prom-client` is now a peer dependency

💣 Breaking changes

• prom-client is now a peer dependency just add it to your dependencies with your package manager of choice

This solves issues with different libraries coming with their own prom-client leading to multiple default registries. This is unintended and can be solved by promster "just" assuming a prom-client being available.