npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@loopback/metrics

v0.14.1

Published

An extension exposes metrics for Prometheus with LoopBack 4

Downloads

16,970

Readme

@loopback/metrics

This module contains a component that reports metrics of Node.js, LoopBack framework, and your application to Prometheus.

Stability: ⚠️Experimental⚠️

Experimental packages provide early access to advanced or experimental functionality to get community feedback. Such modules are published to npm using 0.x.y versions. Their APIs and functionality may be subject to breaking changes in future releases.

Installation

npm install --save @loopback/metrics

Basic use

The component should be loaded in the constructor of your custom Application class.

Start by importing the component class:

import {MetricsComponent} from '@loopback/metrics';

In the constructor, add the component to your application:

this.component(MetricsComponent);

By default, Metrics route is mounted at /metrics. This path can be customized via Metrics configuration as follows:

this.configure(MetricsBindings.COMPONENT).to({
  endpoint: {
    basePath: '/metrics',
  },
  defaultMetrics: {
    timeout: 5000,
  },
  defaultLabels: {
    service: 'api',
    version: '1.0.0',
  },
});

{% include note.html content="this.configure() must be called before this.component() to take effect." %}

It also has to be noted, that by default the OpenAPI spec is disabled and therefore the metrics endpoint will not be visible in the API explorer. The spec can be enabled by setting openApiSpec to true.

this.configure(MetricsBindings.COMPONENT).to({
  openApiSpec: true,
});

Metrics Collected

There are three types of metrics being collected by this component:

  1. Node.js metrics - built-in by https://github.com/siimon/prom-client
  2. LoopBack method invocations - built-in by this module using an interceptor
  3. Metrics by the application code or other modules - instrumentations are required

Pull vs Push

Prometheus supports two modes to collect metrics:

Try it out

git clone https://github.com/loopbackio/loopback-next
npm install
npm run build
cd examples/metrics-prometheus
npm run demo

Open http://localhost:9090 to load Prometheus web UI.

/metrics endpoint

http://localhost:3000/metrics returns metrics in plain text format. It includes information for the Node.js process as well as LoopBack method invocations.

Contributions

Tests

Run npm test from the root folder.

Contributors

See all contributors.

License

MIT